Run singularity test only in merge-queue
Nobody has claimed this yet.
- Dominant language
- Nextflow
- Stars
- 429
- Forks
- 1.1k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 153
Description
Kinda a seperate issue but thought it might be a good place for the discussion.
I was thinking about this in terms of nf-core/modules.
Since we use the merge_queue, what if we only ran singularity and conda when the merge_queue is ran? It seems like the conda environment creation in some modules takes a really long time to get created(and in nf-test it creates the environment every time).
Originally posted by @edmundmiller in #3098
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's merge-queue workflow and nf-test configuration, since the issue names those entry points but no files. Clarify whether Singularity and Conda should run only in merge-queue checks, then define the expected workflow behavior and validation before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100