Update Deployment tests #1268
Merged
Update Deployment tests #1268
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
Samze
force-pushed
the
deployment_tests
branch
2 times, most recently
from
fb2dae3 to
57072e1
Compare
* Use the CLI for Rolling deployments * Add tests for Canary deployments * Add tests for max-in-flight
Samze
force-pushed
the
deployment_tests
branch
from
57072e1 to
ee2e294
Compare
ctlong
approved these changes
Oct 10, 2024
|
Thanks for the speedy review all 👍 |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Are you submitting this PR against the develop branch?
Yes
What is this change about?
What version of cf-deployment have you run this cf-acceptance-test change against?
v42.2.0
Please check all that apply for this PR:
Did you update the README as appropriate for this change?
How many more (or fewer) seconds of runtime will this change introduce to CATs?
More deployment tests, so more time!
What is the level of urgency for publishing this change?