Skip to content

executor.jobName throws an error in nextflow lint #6366

@nvnieuwk

Description

@nvnieuwk

Bug report

Expected behavior and actual behavior

executor.jobName can be used to set the names of specific jobs on grid executors and google cloud batch, while this is still working now it looks like it will be deprecated in the future (nextflow lint throws the following warning: Dynamic config options are only allowed in the 'process' scope). This option is really helpful on Google Cloud Batch and it would be awesome if there is a new supported way to handle this.

Steps to reproduce the problem

Create a config like this:

executor.jobName = { "$task.name - $task.hash" }

Then run nextflow lint <config-name>

Program output

Dynamic config options are only allowed in the `process` scope

Environment

  • Nextflow version: 25.04.6
  • Java version: 17.0.3
  • Operating system: Linux
  • Bash version: (use the command $SHELL --version)

Additional context

(Add any other context about the problem here)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions