build(ci): trigger a deploy of the test API after a successful build #911
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
joker234
added
the
CI
|
matthiasschaub
approved these changes
May 22, 2025
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.
Please add the type of change as label. If your PR is not ready for review and merge, please add
🚧to the PR title.Description
Added a step to the Jenkinsfile to automatically start the test deploy job.
Corresponding issue
None
New or changed dependencies
None
Checklist
main(e.g. throughgit rebase mainif necessary)[ ] My code follows the style guide and was checked with pre-commit before committing[ ] I have commented my code[ ] I have added sufficient unit and integration tests[ ] I have added new Hurl regression tests and checked all existing tests[ ] I have updated the CHANGELOG.md