-
Notifications
You must be signed in to change notification settings - Fork 134
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: bioconductor improvements (#944)
Some fixes identified when preparing for the Bioconductor 3.18 updates: **run_exports.** `bioconductor-skeleton` now adds run_exports to the recipes it builds. Since it's unclear to what extent all bioconductor developers adhere to semantic versioning, I opted for `max_pin="x.x"`, even in the cases where versions start with `0.`. **Better build numbers.** `bioconductor-skeleton update-all-packages` will now only modify the build number if it's needed. It checks what's available in the channel. So running the command multiple times (sometimes needed if the update process flakes out partway through) will not keep bumping the build number. This also uses the same check as the linting, which will hopefully reduce the frequency of build number adjustments in bulk. **Fix manual build failure annotation.** Allow category & reason to show up in manual build failure yaml via `bioconda-utils annotate-build-failures` CLI **More flexible dag.** `bioconda-utils dag` now supports globs. So now with `bioconda-utils dag --packages bioconductor-* | grep -v INFO > dag.gml` and then loading `dag.gml` into [Gephi](https://gephi.org/), you can visually identify which packages should be prioritized for building first. This example sizes nodes by out-degree and labels only those with >125 outgoing edges. ![image](https://github.com/bioconda/bioconda-utils/assets/115406/f2fd2381-59eb-4611-9f67-38d69f731a87) **And minor stuff.** The pinning for bioconductor-data-packages needed a space; there was a build-failure yaml that was empty which crashed osx builds.
- Loading branch information
Showing
4 changed files
with
34 additions
and
19 deletions.
There are no files selected for viewing
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
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
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
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