[JIRA] (JENKINS-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title squalou jenkins commented on JENKINS-39899 Re: workflow-lib : declaring several Libraries causes them to overlap thanks for the link ! sorry I didn"t find the dup. Watching it now. 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-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title squalou jenkins closed an issue as Duplicate Jenkins / JENKINS-39899 workflow-lib : declaring several Libraries causes them to overlap Change By: squalou jenkins Status: Resolved Closed 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-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-39899 workflow-lib : declaring several Libraries causes them to overlap Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-39899 workflow-lib : declaring several Libraries causes them to overlap Change By: Jesse Glick 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-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title
squalou jenkins updated an issue
Jenkins / JENKINS-39899
workflow-lib : declaring several Libraries causes them to overlap
Change By:
squalou jenkins
Workflow lib is great, but still suffers some issues.Several libraries can be defined in Jenkins configuration. This is great. What I plan is :- a global 'core' lib for those boilerplate high level methods everyone need (not many methods, used by lots of people, shared among several jenkins instances)- a 'per jenkins instance' lib, see it as a 'per team' lib for any 'team-specific usecases', if they existMater is : apparently now the lib checkout MUST put 'vars' directory at the root of /jobs/jobId@libsSo, for instance, my libs are on a git repo, I tried to 'checkout in a specific subdirectory' : it doesn't workSo, ok, I leave it in default place ... but then I have to make a 'wipe and force clone' checkout. in the pipeline I would write this :{code:java}@Library ('lib-one')import method1// at this moment, the checkout is done, methods1 becomes available in classpath etc... great@ Livrary Library ('lib-two')import method2//at this moment : lib-two is checked out, lib-one is in the way ... that's where the 'wipe' option is handy, it removes lib-one from disk, even if it's still in memory //without the 'wipe' option, note that there will be a failure here {code}As a result there are several issues :- performance issues : useless git clone performed at each build- hard to setup (I lost hours finding this 'wipe clean chekcout' method- lack of readability : for a post-mortem analysis, lib sources that were used are no more available- rely on repo availability : this is specific to my situation where we have several SCM, the libs are on a 'less critical' one ... and if it's not available then all jobs fail. If I didn't need to wipe lib-one to get lib-two ... next run would simply use the current cached libs.What could work :- either have several @libs dirs, but it's probably not that easy- or correctly follow the 'checkout in subdir' to look for 'vars' etc...
Add Comment
[JIRA] (JENKINS-39899) workflow-lib : declaring several Libraries causes them to overlap
Title: Message Title
squalou jenkins created an issue
Jenkins / JENKINS-39899
workflow-lib : declaring several Libraries causes them to overlap
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline, workflow-cps-global-lib-plugin
Created:
2016/Nov/21 9:06 AM
Environment:
RHEL 7.3 for master jenkins LTS 2.19.3
Priority:
Major
Reporter:
squalou jenkins
Workflow lib is great, but still suffers some issues. Several libraries can be defined in Jenkins configuration. This is great. What I plan is :
a global 'core' lib for those boilerplate high level methods everyone need (not many methods, used by lots of people, shared among several jenkins instances)
a 'per jenkins instance' lib, see it as a 'per team' lib for any 'team-specific usecases', if they exist
Mater is : apparently now the lib checkout MUST put 'vars' directory at the root of /jobs/jobId@libs So, for instance, my libs are on a git repo, I tried to 'checkout in a specific subdirectory' : it doesn't work So, ok, I leave it in default place ... but then I have to make a 'wipe and force clone' checkout. in the pipeline I would write this :
@Library ('lib-one')
import method1
// at this moment, the checkout is done, methods1 becomes available in classpath etc... great
@Livrary('lib-two')
import method2
//at this moment : lib-two is checked out, lib-one is in the way ... that's where the 'wip
