Migrate website build & deploy from Travis-CI to Cloud Build#882
Open
nkinkade wants to merge 2 commits into
Open
Migrate website build & deploy from Travis-CI to Cloud Build#882nkinkade wants to merge 2 commits into
nkinkade wants to merge 2 commits into
Conversation
Adds cloudbuild.yaml and Dockerfile.build so the site builds and deploys via Google Cloud Build instead of Travis-CI. The deploy target is chosen by the triggering project: GCS buckets for sandbox/staging and Firebase Hosting for production, authenticating as the Cloud Build service account (no more SERVICE_ACCOUNT_* key env vars). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Deletes .travis.yml and firebase-deploy.sh (superseded by cloudbuild.yaml), removes the now-unused m-lab/travis submodule, drops the defunct travis-ci.org build badge, and updates CONTRIBUTING.md to describe the Cloud Build pipeline. Adds .gcloudignore for manual 'gcloud builds submit' runs. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Migrate website build & deploy from Travis-CI to Google Cloud Build
Replaces the Travis-CI build/deploy with Google Cloud Build, matching M-Lab's
conventions (per-project triggers,
$PROJECT_IDsubstitution, deploy as theCloud Build service account).
What changes
cloudbuild.yaml— builds the Jekyll site (reusing the existing_tests/travis-checkslogic) and deploys. The deploy target is selected bythe triggering project, guarded by
$PROJECT_ID:mlab-sandbox(push tosandbox-*) → GCSwebsite.mlab-sandbox…mlab-staging(push tomain) → GCSwebsite.mlab-staging…mlab-oti(git tag) → Firebase HostingDockerfile.build— builder image (Ruby 3.1, Node 18 for ther.jsoptimizer, Jupyter/nbconvert for the notebook plugin, firebase-tools).
.travis.yml+firebase-deploy.sh, them-lab/travissubmodule,and the defunct
travis-ci.orgbadge; updateCONTRIBUTING.md.SERVICE_ACCOUNT_*key env vars — deploys authenticate as theproject's Cloud Build service account.
Triggers (already created)
push-m-lab-website-triggerexists inmlab-sandbox,mlab-staging, andmlab-oti. Themlab-otiCloud Build SA was grantedroles/firebasehosting.admin.Testing
gcloud builds submitand trigger-driven build bothpassed — site built and deployed to the sandbox GCS bucket.
from
mlab-oti(auth via ADC worked; live site untouched).Cutover
Merging this PR makes Cloud Build the sole CI/CD for the site and stops Travis
from building it (the config is gone). The staging trigger deploys on merge to
main; the next release tag exercises the production Firebase deploy.This change is