Support multiple nextflow versions in CI

[edmundmiller]

Should we support multiple nextflow versions in the CI? If so which ones. See 8cd635f

[drpatelh]

Good question 👍 Maybe we run against the first stable DSL2 release i.e. 20.07.1 as well as the latest? The pipeline CI tests do something similar but in this instance it ensures that the modules are working across the full spectrum of DSL2 releases. If we encounter breaking changes we can bump the minimum version used for the tests.

[drpatelh]

Note the matrix tests will look something like this

[edmundmiller]

Gotcha! Thanks I couldn't find the right value for "latest"! I'll make another PR once #85 is merged.

[drpatelh]

As a result of the changes introduced in #109 we now have the ability to directly download Singularity containers, however, this functionality was added in an edge release i.e. 20.11.0-edge. This means I had to change the version of Nextflow we use for the module CI as shown in this commit. After the next stable Nextflow release we should revert the CI to using nxf_version: [<STABLE_RELEASE>, ""] again. Note the "" in that list will pull the latest stable release which at this point doesn't contain the functionality we need which is why I removed it in that commit.

[drpatelh]

Hmmmm...after the recent (and superdooper) surge in modules and the failure of all of the current tests to be triggered with one NF version (due to Github Actions matrix limit of 256), I think testing multiple NF versions is overkill until something changes. At which point feel free to re-open this issue.