[ ] If the deleted circle.yml file had a depencencies section, check for repetition of steps from this section in .circleci/config.yml (especially npm install). Repeated steps will slow down builds.
[ ] Debug problems with CircleCI 2.0 build (if needed).
[ ] 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"), there's no need to deploy it now.
If you have any questions or need help debugging, ask in #circleci-1-sunset in slack, look for similar errors in the migration tracking spreadsheet, check out go/circleci-ops, and/or come to CircleCI 2.0 office hours (on the Clever Eng calendar).
Jira
INFRA-3191: migrate non-team-owned repos to CircleCI 2.0
This is an automated PR created with
circle-v2-migratev1.2.0.This PR used the
circle-v2-migratescript to start migrating this repo from CircleCI 1.0 to CirlceCI 2.0.CircleCI 1.0 builds will no longer work after August 31st, so this repo must be migrated to enable builds and deploys after August 31st.
Reviewing & Roll Out Checklist
As the reviewer for your pull request, you own completing the following steps:
[ ] 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.
[ ] If the deleted
circle.ymlfile had adepencenciessection, check for repetition of steps from this section in.circleci/config.yml(especiallynpm install). Repeated steps will slow down builds.[ ] Debug problems with CircleCI 2.0 build (if needed).
[ ] 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"), there's no need to deploy it now.
[ ] 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.)
If you have any questions or need help debugging, ask in #circleci-1-sunset in slack, look for similar errors in the migration tracking spreadsheet, check out go/circleci-ops, and/or come to CircleCI 2.0 office hours (on the Clever Eng calendar).