TRU-327: Migrate CI/CD from Azure Pipelines to GitHub Actions - #33
Open
jtcrde wants to merge 1 commit into
Open
Conversation
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
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.
Summary
Migrates this repo's CI/CD off Azure Pipelines (which relies on the shared
pipeline-libraryand runs inquantumci.azurecr.io/quantum-ci-terragruntcontainers) onto a self-contained GitHub Actions workflow at.github/workflows/ci.yaml. Follows the patterns established inmigration-plan.mdandinfrastructure-live-staging/.github/workflows/run-regression.yaml.Changes
.github/workflows/ci.yamlazure-pipelines.ymlBehavior parity with the old pipeline
AzureKeyVault@1+import-ssh-key.ymlsecrets.QUANTUM_CI_BOT_GITHUB_SSH_KEYinit-git-submodules.ymlactions/checkoutsubmodules: recursivepre-commit run --all-filesnpm ci+ global linkssetup-node+npm install -gsemantic-release toolchainrun-ci-analysis.yml(--quiet --soft-fail)checkovcall (--quiet --soft-fail,continue-on-error)semantic-release.ymlnpx semantic-releaseon master/mainupdate-source-reference.yml?ref=, GPG-signed commit, direct push for minor/patch, PR for majorrunFunctionalTests: false)Why
timeoutInMinuteshard-cap fromterraform.ymltemplate (nowtimeout-minutes: 30).package-*terraform repos when their migration turn comes.Required secrets (must be present on the repo or org)
QUANTUM_CI_BOT_GITHUB_SSH_KEYQUANTUM_CI_BOT_GITHUB_TOKENQUANTUM_CI_BOT_NPM_TOKENIMPORT_GPG_KEY,IMPORT_GPG_KEY_ID,IMPORT_GPG_KEY_PASSPHRASE,IMPORT_GPG_KEY_SUBJECTTest plan
semantic-releaseandUpdate infrastructure-modules referencessteps are skipped on non-master