[tests] and different operation modes to integration testing script #27
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
Previously, `./run_integration_tests.sh` would build a release tarball of all the provisioning binaries, along with container images containing each provisioning binary, and then unpack the binaries into the deployment staging area, even if only the containers were run. This was slow when debugging because compressing and uncompressing binaries (that are not even used) is slow. This adds a `-c` mode to the `./run_integration_tests.sh` to only build an deploy the container images to save time when debugging. Additionally, a `-d` (debug) mode is added that prevents the containers from being torn down on script exit to enable debugging test failures. Signed-off-by: Tim Trippel <[email protected]>
moidx
approved these changes
Oct 2, 2024
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.
Previously,
./run_integration_tests.shwould build a release tarball of all the provisioning binaries, along with container images containing each provisioning binary, and then unpack the binaries into the deployment staging area, even if only the containers were run. This was slow when debugging because compressing and uncompressing binaries (that are not even used) is slow.This adds a
-cmode to the./run_integration_tests.shto only build an deploy the container images to save time when debugging.Additionally, a
-d(debug) mode is added that prevents the containers from being torn down on script exit to enable debugging test failures.