First steps for pipelines #20
Merged
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
Closed
This implements a basic Create-Read-Update-Delete database for pipeline statuses. This can be used to check that status of a particular pipeline, so that it could potentially be revived after a killed job. Some caveats: * Python ID is used for each pipeline. I am not sure if this is a good idea since the ID might be unique for each run. The `create` is somewhat wrong, it could also update and is not strictly separated. Can be fixed later on. Tests auto-generated by GitHub, seem to cover at least the very basics. More sophisticated tests will come later on. Signed-off-by: Paul Gierz <[email protected]>
siligam
approved these changes
Jul 23, 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.
Very basic steps for pipelines for creation of CMORized data. Still to come: