-
Notifications
You must be signed in to change notification settings - Fork 145
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 CI and Changelog #433
Conversation
|
.github/workflows/ci.yml
Outdated
@@ -35,6 +35,7 @@ jobs: | |||
- "24.04.2" | |||
- "latest-everything" | |||
shard: [1, 2, 3, 4, 5] | |||
filter: [process, workflow] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pipeline-level tests are not included?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah good catch! should be pipeline and workflow
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And process? I think the idea is to test everything?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think its gonna overload the CI runners with too many tests to run
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we have to bank on the fact that the modules were/are tested in the modules repo and the pipeline CI runs only pipeline and workflow tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should bring this up in the #nf-test
channel and we can discuss/vote there
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What if there are local modules with tests? Moreover, the tests are only triggered for the changed modules.
If there are no local modules or functions with tests, let's skip process
.
One more thing. If the nextflow.config changes or something from the assets
directory changes, will the pipeline-level tests be triggered? I like the CI of nf-core/rnaseq which checks for these changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz bring this up in the nf-test
channel and lets discuss there and get some consensus
LGTM! |
No description provided.