-
Notifications
You must be signed in to change notification settings - Fork 206
Add CI tests to test running a pipeline when it's created from a template #2334
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
Conversation
…ate skipping different areas
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 speaks against adding this test to create-test-wf.yml
instead of having it in a separate file?
Can do both, I just found it more organized in a different file |
Codecov Report
@@ Coverage Diff @@
## dev #2334 +/- ##
=======================================
Coverage 73.08% 73.08%
=======================================
Files 78 78
Lines 8779 8784 +5
=======================================
+ Hits 6416 6420 +4
- Misses 2363 2364 +1
|
Actually, because these pipelines created from a template are unbranded, the pipeline prefix is different, so I think it's easier to have two separate files |
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.
should also only run if the pipeline template was actually changed:
on:
push:
paths:
- nf_core/pipeline-template/**
Everything working now! 🥳 |
This is a test to see if it's viable to add CI tests for all possible templates:
➕ We could also add the same for linting.
⚠️ It will take considerably more time and Github runners, so needs to be discussed before merging.
👁️ This will make sure that bugs as the ones found recently (#2332 and #2333) are not repeated.
PR checklist
CHANGELOG.md
is updateddocs
is updated