I followed the instructions to get the workflowLibs.git repository from
Jenkins:
SInce the repository was empty I got nonexistent ref as expected and
mentioned in the instructions.
sverre@mintaka:~/workspace> git clone
https://build.company.com:8443/workflowLibs.git
Cloning into 'workflowLibs'
Yes, that explained a lot. Thanks.
lørdag 28. mai 2016 02.11.53 UTC+2 skrev Kohsuke Kawaguchi følgende:
>
> See https://github.com/jenkinsci/workflow-cps-global-lib-plugin
>
> Hope that helps!
>
> On Thu, May 26, 2016 at 12:37 AM Sverre Moe > wrote:
>
>> Yes, I came across it, but there is so lit
See https://github.com/jenkinsci/workflow-cps-global-lib-plugin
Hope that helps!
On Thu, May 26, 2016 at 12:37 AM Sverre Moe wrote:
> Yes, I came across it, but there is so little information about how to use
> this and how it works.
> The only thing I could find was this example here
> https:/
Yes, I came across it, but there is so little information about how to use
this and how it works.
The only thing I could find was this example
here
https://github.com/jenkinsci/pipeline-examples/tree/master/global-library-examples/global-function
which I did not understand much of.
// The call
Did you possibly have a look at:
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Remote+Loader+Plugin
or
https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Shared+Groovy+Libraries+Plugin
?
2016-05-24 16:00 GMT+02:00 Sverre Moe :
> What is the best design approach to keeping the Jenkinsfile
What is the best design approach to keeping the Jenkinsfile small (little
build logic as possible)?
Having close to a hundred projects and several branches on each, then
duplicating the pipeline logic within each Jenkinsfile would be a
maintenance nightmare.
1)
I could put the Pipeline script
