[INFRA-3186] autotranslate CircleCI 1.0 -> 2.0#8
Merged
Conversation
6423454 to
bc1bdde
Compare
625a61b to
cdd26f5
Compare
3271f45 to
dfddb84
Compare
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.
Jira
INFRA-3186: migrate infra repos to CircleCI 2.0
Overview
This is an automated PR created with
circle-v2-migratev1.1.0.CircleCI 1.0 is sunsetting August 31st, meaning CircleCI 1.0 builds will no longer work on September 1st.
This PR uses the output of the
circle-v2-migrateautomigration script, withmicroplane, to translate the build config from circle.yml to CircleCI 2.0's format and file location.This PR should not make any changes to application code. All test, build, publish, and deploy steps from
circle.ymlshould have been preserved in the translation.If you have any questions, please post in the #circleci-1-sunset channel in slack, and/or join the CircleCI 2.0 migration office hours (see Clever Eng calendar).
Reviewing & Roll Out Checklist
New: check for redundant steps if
circle.ymlhad adepencenciessection. Repeated steps should not break code, but they do lead to slower builds.If this repo should be graveyarded, add it to the "graveyard" team in the CircleCI 1.0 -> 2.0 migration tracking spreadsheet and close this PR.
Debug problems with CircleCI 2.0 build (if needed). Check out go/circleci-ops, #circleci-1-sunset in slack, and/or CircleCI 2.0 office hours (on the Clever Eng calendar) for help.
Merge this pull request when the build passes.
Deploy as normal for this repository. If the repo's code is not currently deployed (e.g., Dapple says "first deployment"), don't deploy it.
Optional: update this repo's row in the CircleCI 1.0 -> 2.0 migration tracking spreadsheet. (If you don't manually update, the change should show tomorrow.)