New field: Set Nextflow version
acknowledged
Phil Ewels
At the moment if you want to fix a Nextflow version, you have to use a pre-run script to export the
NXF_VER
environment version. This is fine, but it's not intuitive for what is a fairly central part of the experience of running Nextflow on Seqera Platform.Suggestion is to have a new field in the UI to set the Nextflow version. This could potentially be when creating a new Compute Environment, ideally with a secondary field which could be set when launching a workflow (either to set new or to override the default in the CE).
The field should default to using the latest stable release of Nextflow, but give the option of using the latest edge release instead, or a specified exact release version.
Rob Newman
acknowledged
Adam Talbot
As an additional benefit, it makes it clear the platform is compatible with more than 1 version of Nextflow. Currently, the UX implies you must use the 'matching' version and anything else is a hacky workaround, which isn't the case.