Add scripts for downstream testing#408
Merged
Merged
Conversation
9f4c799 to
2e2a040
Compare
nicoddemus
reviewed
Jun 20, 2023
| Release Procedure | ||
| ----------------- | ||
|
|
||
| #. Dependening on the magnitude of the changes in the release, consider testing |
Member
There was a problem hiding this comment.
Perhaps we should have a workflow which runs them all in parallel? This workflow can then be triggered manually and perhaps also in a cron and/or merge with main.
Member
Author
There was a problem hiding this comment.
Yes that would be good, but I am too lazy to do that ATM, but wanted to at least make it possible to test locally for now.
Member
Author
|
BTW if you have other projects we might want to test, let me know. I know of airflow but I had some trouble setting it up. |
nicoddemus
approved these changes
Jun 20, 2023
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
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.
Fix #406