[JIRA] (JENKINS-41188) [Pipeline] External libraries should be able to declare dependencies

[ssutherland@ea.com (JIRA)]

Sean Sutherland created an issue

Jenkins / JENKINS-41188 [Pipeline] External libraries should be able to declare dependencies Issue Type: Improvement Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2017/Jan/18 11:07 PM Priority: Minor Reporter: Sean Sutherland Pipeline libraries should be able to declare dependencies on other external libraries, so that the Jenkins configuration doesn't have to manage the entire version set. This would allow for safer adoption of new versions of libraries. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[ssutherland@ea.com (JIRA)]

Sean Sutherland commented on JENKINS-41188

Re: [Pipeline] External libraries should be able to declare dependencies One option would be to let external libraries use the @Library annotation, and thus have the dependency resolution occur at compile/run time. Alternately, libraries could define their dependencies in a data/groovy/json file in a predetermined location, and then the validation could be done statically.

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick resolved as Won't Do

Not going there. If your libraries are getting complicated enough to require package management, switch to writing a plugin.

Jenkins / JENKINS-41188

[Pipeline] External libraries should be able to declare dependencies

Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do

Add Comment

[swatts24@bloomberg.net (JIRA)]

Simon Watts commented on JENKINS-41188

Re: [Pipeline] External libraries should be able to declare dependencies We host a large cluster of Jenkins servers (250+), used by a host of projects (750+ on my instance, with many branches!). Most extension libraries are not complex but may quite easily use steps provided by plugins.  Sharing these across teams and instances needs coordination of plugin management. So its an issue with horizontal rather than vertical scaling.  Declaring what plugins you depend on is good practice.  If this is the case, then having Jenkins read a source and check it against its plugins seems logical.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)