jenkinsci/jenkinsfile-runner

Document ways to include shared libraries when running jenkinsfile-runner

Open

#204 opened on Oct 17, 2019

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Java (1,090 stars) (291 forks)batch import
documentationgood first issuequestion

Description

Just curious if there is anyway to load shared-libraries when jenkinsfile-runner invokes the pipeline. I read the comment below from (#23) from a year go, wondering if not currently supported would it be in the roadmap?

jenkinsfile-runner in it's current design only can run a Jenkinsfile that can execute on a green field jenkins installation without any specific setup. So tons of use cases won't be supported, like using tool installations, credentials, variables, plugins with specific configuration, and ... shared libraries.

For those, we need jenkinsfile-runner to include some jenkins configuration, and I indeed would like to get JCasC used for this purpose.

Contributor guide

Tech stack
java
Domain
clici cd
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with JenkinsBasic command line usage
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Review the comment in issue #23 regarding the current design limitations. Investigate the Jenkinsfile Runner codebase (e.g., the source files in src/) to confirm if shared library loading is implemented. If not, document the limitation and suggest using JCasC for configuration, as mentioned in the maintainer's comment. Update the README or wiki accordingly.