-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update installation #363
Merged
Merged
Update installation #363
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
😄 thanks, very useful |
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.
Created scripts to scan the repository to get the Python, R and 3rd-party dependencies and generates a conda environment file with them. The output is kept under the folder "conda/environments".
The goal is to use conda environment files to deploy CGAT code everywhere. Hopefully this will offer portability (easier to install the code out of CGAT systems) and reproducibility (code and runtime environment under version control). Combining this with nosetests and pipeline_testing, we will be able to easily check in advance whether software updates will break existing code or produce different results.
Briefly, this is how it works:
grep "library(r-package)"
snakefood
statement = "commands"
(usingAbstract Syntax Trees
). Anything called in a different way will not be picked up.The approach is far from perfect, but gives an automatic way of getting dependencies. Happy to hear more advance solutions for doing this.
During the Python 3 migration we shortlisted a subset of production pipelines. Of those, not all of them are being tested with Jenkins. Right now, the conda installation will only cover those pipelines with Jenkins tests (sorry!) but I am happy to assist with the creation of new tests for the remaining pipelines.
Here is the list of pipelines with a supported conda installation:
Below is a list of the conda environments. Please let me know if you see missing dependencies, as my scripts might have skipped important ones.