Pipeline promotions designs #76
Merged
Conversation
This file contains 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
enekofb
reviewed
Sep 21, 2022
enekofb
reviewed
Sep 21, 2022
enekofb
force-pushed
the
promotions-comparison
branch
from
235c299 to
bb0dc4a
Compare
enekofb
force-pushed
the
promotions-comparison
branch
from
914c685 to
fb57569
Compare
3 tasks
enekofb
reviewed
Oct 6, 2022
enekofb
reviewed
Oct 7, 2022
enekofb
reviewed
Oct 7, 2022
enekofb
reviewed
Oct 7, 2022
enekofb
reviewed
Oct 7, 2022
enekofb
reviewed
Oct 7, 2022
enekofb
reviewed
Oct 7, 2022
|
|
||
| ## Summary | ||
|
|
||
| Given a continuous delivery pipeline, the application goes via different environments in its way to production. We |
There was a problem hiding this comment.
From @pfcurtis
The second option would be more broadly applicable now, as many of the prospects we have already have CI pipelines in place. To have a callback to their CI when the application is deployed would be easy to implement with most any CI tooling.
The first option would require some thinking ... especially around staged deployments or flagger rollouts. I think it would be potentially harder to rollback, if a problem occurs. Just my 2¢
enekofb
reviewed
Oct 20, 2022
| kind: HelmRelease | ||
| name: podinfo | ||
| promotion: | ||
| pullRequest: |
There was a problem hiding this comment.
extend the spec to have a configurable strategy on how to handle multiple PRs not merged
sympatheticmoose
approved these changes
Oct 24, 2022
yiannistri
commented
Oct 25, 2022
docs/rfcs/0003-pipelines-promotion/detect-deployment-changes.md
Outdated
Show resolved
Hide resolved
enekofb
approved these changes
Oct 25, 2022
Co-authored-by: Yiannis <8741709+yiannistri@users.noreply.github.com>
Co-authored-by: Yiannis <8741709+yiannistri@users.noreply.github.com>
makkes
reviewed
Oct 26, 2022
Co-authored-by: Max Jonas Werner <makkes@users.noreply.github.com>
Co-authored-by: Max Jonas Werner <makkes@users.noreply.github.com>
Co-authored-by: Max Jonas Werner <makkes@users.noreply.github.com>
Co-authored-by: Max Jonas Werner <makkes@users.noreply.github.com>
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.
closes weaveworks/weave-gitops-enterprise#1614