cloudfoundry/routing-ci

Name: routing-ci

Owner: Cloud Foundry

Description: null

Created: 2017-07-06 19:22:50.0

Updated: 2018-05-24 15:27:21.0

Pushed: 2018-05-24 15:27:19.0

Homepage: null

Size: 255

Language: Shell

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

routing-ci

Public configuration for the CF Routing team's CI pipelines

CI Dashboard: dashboard.routing.cf-app.com

Dashboard config

DNS

• cf-app.com base domain includes an NS record that delegates routing.cf-app.com to DNS Zone routing-team
• CNAME record axxxxxxxl.routing.cf-app.com is required for domain verification. If you remove it, everything breaks!
• Then dashboard.routing.cf-app.com is a CNAME for c.storage.googleapis.com in order to support GCP Static Website Hosting

Storage

• There's a GCP storage bucket for dashboard.routing.cf-app.com
• It is configured to serve the contents of the index.html file in the storage bucket
• That file defines a simple iframe that uses the htmlpreview.github.io

   dashboard.routing.cf-app.com
  
  iframe src="http://htmlpreview.github.io/?https://github.com/cloudfoundry/routing-ci/blob/master/public-dashboard.html"></iframe>
  

• the html preview is of the public-dashboard.html file in this repo
• 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.