[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Christoph Obexer commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements While commenting on JENKINS-49651 I had an idea that could make this almost automatic: Extend plugin metadata with (RPM style) Provides for pipeline symbols (& extensions,... ) they implement. With that metadata available in the Update Center a build that tries to use say the junit step could instead of failing the build be paused and the user could be prompted if they want to install the plugin that provides that step of if they want to abort the build: Pipeline execution detects unknown step / use of a global / unknown type referenced. Pipeline execution paused (like with an input step?) Query Update Center metadata if there are plugins that provide the missing references Prompt the user to install those plugins or fail the build (possibly saving ignored dependencies) User selects to install the missing plugins -> continue the pipeline execution maximum user satisfaction Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Baptiste Mathus commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements Unassigned myself to clarify I'm not working on this currently. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-34002 Means of declaring a Pipeline's plugin requirements Change By: Baptiste Mathus Assignee: Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Patrick Wolf started work on JENKINS-34002 Change By: Patrick Wolf Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Patrick Wolf assigned an issue to Baptiste Mathus Jenkins / JENKINS-34002 Means of declaring a Pipeline's plugin requirements Change By: Patrick Wolf Assignee: Jesse Glick Baptiste Mathus Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Baptiste Mathus commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements Proposal in https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/31 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34002 Means of declaring a Pipeline's plugin requirements Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Liam Newman commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements So, we're disagreeing about whether to have a generic require or a plugin specific one? What about implementing the generic syntax, but with only plugin name for now? require plugin: 'junit-plugin' Then we have the concept and can consider expanding it (or not) later? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-34002 Means of declaring a Pipeline's plugin requirements Change By: Liam Newman Comment: I assume this is a way of asserting that specific plugin (or specific version of a plugin) must be present. The script shouldn't be able to install a plugin, only give a meaningful error if it isn't. I disagree that things that are required can be handled by individual steps. Having to wait until mid-pipeline to get a "nohup" error because you're missing some configuration is extremely frustrating. Groovy and Java coding guidelines enforce "import"s at the top (not in the middle of the file), the same should be true of pipeline. Fail fast with a meaningful message at the beginning of a pipeline when you know you're going to fail because you're missing a plugin is consistent and vastly better behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Liam Newman commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements I assume this is a way of asserting that specific plugin (or specific version of a plugin) must be present. The script shouldn't be able to install a plugin, only give a meaningful error if it isn't. I disagree that things that are required can be handled by individual steps. Having to wait until mid-pipeline to get a "nohup" error because you're missing some configuration is extremely frustrating. Groovy and Java coding guidelines enforce "import"s at the top (not in the middle of the file), the same should be true of pipeline. Fail fast with a meaningful message at the beginning of a pipeline when you know you're going to fail because you're missing a plugin is consistent and vastly better behavior. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
