jenkinsci/jenkinsfile-runner

Pin Jenkinsfile Runner versions in demos

Open

#261 opened on Apr 2, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (1,090 stars) (291 forks)batch import
demodocumentationgood first issue

Description

Currently Jenkinsfile Runner demos use the runner version from the local repository. So each demo basically needs an update every time an incompatible version is released. It would be better to support delaying the demo updates by using an explicit Jenkinsfile Runner version definitions in all Custom War Packager config files

Contributor guide

Tech stack
java
Domain
ci cddevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
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.
mostly clear
Prerequisites
Knowledge of Jenkinsfile RunnerCustom War Packager config files
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
The issue requests pinning Jenkinsfile Runner versions in Custom War Packager config files under the demo directory. It currently uses the local repository version, causing incompatibility. The solution is to add explicit version definitions in those config files. The maintainer may clarify which specific config files and version strategy to use. Check existing config files and the project's versioning approach.