-
Notifications
You must be signed in to change notification settings - Fork 54
Description
Description of feature
The current DIA workflow does not support the Conda platform. Only the ID, DDA-LFQ, and DDA-TMT can be run in the three platforms Conda, Docker, and Singularity. However, this tree workflow heavily depends on the OpenMS platform to do the releases for us to do the release.
OpenMS team @timosachsenberg has mentioned that the most difficult for OpenMS to release is the Conda platform. They can nightly release docker and singularity. This situation prompts the following issues:
- Delay our releases waiting for OpenMS's big release.
- When a bug is found and @timosachsenberg (OpenMS) team fixes it, we have to wait a year to get it.
Multiple pipelines in nf-core are not supporting anymore Conda (https://nfcore.slack.com/archives/C04QR0T3G3H/p1744360287778109) and we do in fact not support it for DIA. Knowing this. I will propose the following flow:
- Enable a CI/CD that enables to pull from (ghcr.io/openms/openms-tools-thirdparty-sif:latest) OpenMS Docker and Singularity container and
tagit with the date:Y.M.D, push the containers to quantms ghcr.io space. - Have a mechanism to disable on specific releases Conda. The idea is that we can have released with Conda support and others without Conda support (when OpenMS is available). The other option is to disable the Conda until more people/users complain about this issue.
Would be good to have a feedback here, with comments.