Containerization of workflow #97
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
…pplementary workflow scripts
fix: split rules to separate dependencies
fix: split combined job to separate script-based job for better dependency management
ci: add supplementary scripts for container build process
…g list() to fix compatibility of root-paths
…conda or containers) fix: properly set the readline tabcompleter
…e snakemake_run_con object to properly access it from within workflows
…nakemake_run_conf object feat: add singularity arguments to snakemake config fix: pass the snakemak configuration settings in a dictionary to the snakemake workflow itself style: formatting with isort & black feat: handle the downloading of containers in the viroconstrictor wrapper
…nakemake_run_conf object feat: add singularity arguments to snakemake config for main workflow fix: pass the snakemake configuration settings in a dictionary to the main snakemake workflow itself feat: handle the downloading of containers necessary for main workflow in the viroconstrictor wrapper
Refactor the GitHub Actions workflows to update the triggers for container publishing. Change the trigger for the "build_and_test.yml" workflow to only run on pull requests to the main branch. Additionally, add a new workflow "publish_containers.yaml" to handle the publishing of containers. This workflow will be triggered on pushes to the dev branch. Related recent commits: - ci: change upstream registry - ci: temporarily add listing of directory contents for debugging purposes - ci: add step in container build/test workflow to download already existing containers
…omamba shell in GH actions
The `download_containers` function in the `containers.py` module has been refactored to include better error handling and logging. Previously, if a container failed to download, the function would return a non-zero status code without providing any specific error message. Now, when a container fails to download, the function logs an error message indicating the name of the container that failed. This change improves the clarity of error reporting and makes it easier to troubleshoot container download issues. Related recent commits: - refactor: add verbose option to `download_containers` function - ci: temporarily add listing of directory contents for debugging purposes - ci: add step in container build/test workflow to download already existing containers
|
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.
✨