[JIRA] [workflow-plugin] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements

[ty...@monkeypox.org (JIRA)]

Title: Message Title

R. Tyler Croy commented on JENKINS-34002   Re: Means of declaring a Pipeline's plugin requirements I've been thinking a lot about this general idea the past couple weeks, and had even considered writing a plugin last weekend before I got sick I think a more generic "require" syntax would be ideal for example: require 'junit' /* plugin artifactId */ require 'parallel-text-executor' Which could be expanded upon with the keyword arguments in groovy to support additional requirement statements in the future, e.g. /* Naturally all of these could be squished into one require statement */ require plugin: 'junit' require core: '1.642.4' require tool: ['Maven' : '3.3.3'] I'm curious what Patrick Wolf and Andrew Bayer think of this syntax. The simplest approach would simply be a step which fails if some of the requested plugins are missing or too old: Mostly agreed, i suggest that the pipeline should abort because of missing dependencies with console outputs stating this Jenkins instance is lacking the required dependencies to execute this pipeline. I generally interpret failures to mean the Pipeline is broken (user error) rather than something requiring a user/administrator cooperation to rectify. I don't have much better reasoning than that, but an abort would catch my gaze a lot sooner than a failure, unfortunately As far as version restricting goes, in my mind I was thinking on punting on that for now until some more users using any require syntax. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.