Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-56270] - Support Including shared libraries in Jenkinsfile Runner #124

Open
belsander opened this issue Apr 19, 2018 · 8 comments
Labels
enhancement New feature or request

Comments

@belsander
Copy link

Hi,

Thanks for the work! I'm however looking into including a shared library to validate our Jenkinsfiles, but I do not know how to proceed. Could you help me out?

Thanks!

@OliverNocon
Copy link

Hi,

You could do this by using JCasC plugin and define your lib in the config.yml.
Here the example how the lib details can be defined:
https://github.com/jenkinsci/configuration-as-code-plugin/tree/master/demos/workflow-cps-global-lib.
Best regards.

@fwilhe
Copy link

fwilhe commented Feb 12, 2019

Hey @belsander,

in the meantime this is really easy to solve using Configuration as Code as mentioned by @OliverNocon. I've described it for a specific case in a blog post, should be really simple to adopt for other cases. I think this issue can be closed.

@oleg-nenashev
Copy link
Member

My plan is to have support of packaging libraries with Custom WAR Packager flow: https://issues.jenkins-ci.org/browse/JENKINS-56100

https://jenkins.io/blog/2018/10/16/custom-war-packager/ explains the flow for custom packages

@oleg-nenashev
Copy link
Member

@fwilhe Just in case you are interested, your blog could be reposted on https://jenkins.io/node/ . It would be an interesting case study. CC @tracymiranda

W.r.t rhis particular issue, I am going to close it. JCasC formally addresses the request (see the blogpost), the rest will be automated in https://issues.jenkins-ci.org/browse/JENKINS-56100 .

@fwilhe
Copy link

fwilhe commented Feb 22, 2019

@oleg-nenashev @tracymiranda I'd love to share the post in other places. What would I need to do for that?

@oleg-nenashev
Copy link
Member

@fwilhe We use configuration-as-code so you can just submit a pull request to https://github.com/jenkins-infra/jenkins.io. Guidelines: https://github.com/jenkins-infra/jenkins.io/blob/master/CONTRIBUTING.adoc#adding-a-blog-post

@fwilhe
Copy link

fwilhe commented Feb 22, 2019

Submitted a PR :)

Thanks for the offering!

@oleg-nenashev oleg-nenashev changed the title Include shared library [JENKINS-56270] - Include shared library Sep 19, 2019
@oleg-nenashev oleg-nenashev changed the title [JENKINS-56270] - Include shared library [JENKINS-56270] - Support Including shared libraries Sep 19, 2019
@oleg-nenashev oleg-nenashev reopened this Sep 19, 2019
@oleg-nenashev oleg-nenashev transferred this issue from jenkinsci/jenkinsfile-runner Sep 19, 2019
@oleg-nenashev oleg-nenashev changed the title [JENKINS-56270] - Support Including shared libraries [JENKINS-56270] - Support Including shared libraries in Jenkinsfile Runner Sep 19, 2019
@oleg-nenashev oleg-nenashev added enhancement New feature or request hacktoberfest labels Sep 19, 2019
@oleg-nenashev
Copy link
Member

Removing Hacktoberfest label, because the easiest way (Filesystem SCM Plugin) has a published unresolved security issues. Ideally it needs a proper solution on the Pipeline Side instead (Lirary Source extension)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants