-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Convert to new split pipeline approach for CI/CD #278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
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
daniel-hanson
approved these changes
Jun 10, 2020
commit 01af8da Author: j-so <[email protected]> Date: Fri Jun 12 14:15:35 2020 -0700 fixed failure handling commit 1e6f906 Author: j-so <[email protected]> Date: Fri Jun 12 14:03:09 2020 -0700 test failed conda dep commit a8030d7 Author: j-so <[email protected]> Date: Fri Jun 12 13:55:00 2020 -0700 test package fail commit c7845aa Author: j-so <[email protected]> Date: Fri Jun 12 13:46:27 2020 -0700 fail on deploy error'
dtzar
suggested changes
Jun 15, 2020
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the CI steps are identical, I believe we should keep thing consistent by having a CI and then a CD pipeline which is triggered when the CI pipeline is complete. Sooo... This means for this PR:
- No need for a separate "getting started doc"
- Remove duplicate CI pipeline, fix the existing one to move the CD steps into a "Task based deployment" pipeline.
- Fix the main getting started guide to ask people if they want the AzDO task deployment or Az CLI deployment, setting whatever you feel is the best default one triggered by the CI pipeline. If you feel the engineering team doesn't want people to have the task deployment, then go ahead and remove this choice.
dtzar
reviewed
Jun 15, 2020
commit 5af6eeb Author: j-so <[email protected]> Date: Mon Jun 15 18:31:15 2020 -0700 fix bootstrap commit f61e103 Merge: 2796b40 08bb6f4 Author: j-so <[email protected]> Date: Mon Jun 15 18:30:21 2020 -0700 Merge branch 'master' into jenns/splitpipeline_docfix commit 2796b40 Author: j-so <[email protected]> Date: Mon Jun 15 18:30:00 2020 -0700 remove old pipeline commit 08bb6f4 Author: David Tesar <[email protected]> Date: Mon Jun 15 14:09:12 2020 -0700 Simplify docs flow (#297) commit cd762ec Author: jotaylo <[email protected]> Date: Mon Jun 15 12:28:23 2020 -0700 Move instruction to install AML extension to Azure Devops setup instructions (#298)
dtzar
reviewed
Jun 17, 2020
dtzar
approved these changes
Jun 17, 2020
commit 493ed3e Author: j-so <[email protected]> Date: Mon Jun 22 16:42:07 2020 -0700 mark as output commit 1ca7a59 Author: j-so <[email protected]> Date: Mon Jun 22 16:12:10 2020 -0700 fix import commit 743e301 Author: j-so <[email protected]> Date: Mon Jun 22 15:59:43 2020 -0700 more fixes commit 44abcac Author: j-so <[email protected]> Date: Mon Jun 22 15:50:49 2020 -0700 fix batch scoring
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.
Introduces a new set of pipelines that split model/train/eval and deployment.
NOTE: There is a limitation with the model deployment pipeline. It relies solely on the output of the model training pipeline. Right now it cannot run off the model name/version env vars.
Also addresses #274