-
Notifications
You must be signed in to change notification settings - Fork 201
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
AWS full tests #3462
Comments
Agree - sounds like it's suffered a bit of drift since it was first written. My memory from when we added it was that it'd run in two circumstances:
I think that the PR stuff was probably added in later, as folks weren't running it manually and failures would show up post-release. The idea was that Now that we are in a happy place with AWS credits, I think that it's a good idea to test on PRs and release as you say @mirpedrol So to confirm, you're suggesting removing these lines: tools/nf_core/pipeline-template/.github/workflows/awsfulltest.yml Lines 7 to 10 in 52e8109
But keeping these? tools/nf_core/pipeline-template/.github/workflows/awsfulltest.yml Lines 12 to 13 in 52e8109
Note that tools/nf_core/pipeline-template/.github/workflows/awsfulltest.yml Lines 18 to 19 in 52e8109
I don't really understand the bit about launching pipelines from
Is this not doing the correct thing - launching from the PR merge dev if in a PR and launching from the latest commit when on release? |
Yes, sorry, there was a mistake in my text. Currently, this action is launching the pipelines from a git sha, which is the merge commit, and thus it doesn't exist in the pipeline. |
The github action to launch the pipeline with full tests in AWS with the Seqera platform has some issues right now:
pull_request
doesn't make sense as it's always skipped. The action will only run if there are two reviews or if it's manually dispatched. This can be removed.The text was updated successfully, but these errors were encountered: