[INFRA-3186] autotranslate CircleCI 1.0 -> 2.0#15
Open
bgveenstra wants to merge 1 commit intomasterfrom
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.
Jira
INFRA-3186: migrate infra repos to CircleCI 2.0
Overview
This is an automated PR created with
circle-v2-migratev0.8.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.
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
Please merge this pull request when you are ready, then deploy as usual for this repo.
All test, build, publish, and deploy steps should have been preserved in the translation.
There is a small chance the build may fail on master. If the build fails, please link to this PR or to the failing build in this repo's row in the CircleCI 1.0 -> 2.0 migration tracking spreadsheet and post in #circleci-1-sunset in slack.