CICD: add Jenkins pipeline for automated stage deployment #142
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
jordanpadams
approved these changes
Feb 15, 2023
tloubrieu-jpl
changed the title
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.
🗒️ Summary
Support end-to-end integration tests on Jenkins by adding a
Jenksfilepipeline which builds, installs, unit-tests, and the integration-tests thepds-deep-registry-archivesoftware against the expo registry.⚙️ Test Data and/or Report
See this failed run which is expected because pagination is currently broken in the Registry.
Also note that the above run was run by hand, because the upstream pipeline (Registry) is failing and the Deep Archive project is set to be triggered only in the case of a successful upstream run.
♻️ Related Issues