that file contains its own iframes to show various views from our Concourse server
Why use two layers of indirection?
We could put the Concourse iframes directly in the index.html file. But that file is difficult to update: you have to use the GCP console, or GCP API. This way, we can make changes to the dashboard layout with a simple git push to this repo.
Helper Scripts
There are a handful of helper scripts and functions in the /scripts directory. To use them, add the directory to your path and source the directory:
routing-ci
Deprecation Notice
This repo is deprecated. If you use tasks or pipelines in this repo, please reach out to cf-networking@pivotal.io
Public configuration for the CF Routing team’s CI pipelines
CI Dashboard:
dashboard.routing.cf-app.comDashboard config
DNS
cf-app.combase domain includes an NS record that delegatesrouting.cf-app.comto DNS Zonerouting-teamaxxxxxxxl.routing.cf-app.comis required for domain verification. If you remove it, everything breaks!dashboard.routing.cf-app.comis a CNAME forc.storage.googleapis.comin order to support GCP Static Website HostingStorage
dashboard.routing.cf-app.comindex.htmlfile in the storage bucketiframethat uses thehtmlpreview.github.iopublic-dashboard.htmlfile in this repoiframes to show various views from our Concourse serverWhy use two layers of indirection?
We could put the Concourse iframes directly in the
index.htmlfile. But that file is difficult to update: you have to use the GCP console, or GCP API. This way, we can make changes to the dashboard layout with a simplegit pushto this repo.Helper Scripts
There are a handful of helper scripts and functions in the
/scriptsdirectory. To use them, add the directory to your path and source the directory:For
cf_loginandbosh_loginto environments:For local bosh-lite management: