jenkinsci/jenkinsfile-runner

Pin Jenkinsfile Runner versions in demos

Open

#261 建立於 2020年4月2日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Java (1,090 star) (291 fork)batch import
demodocumentationgood first issue

描述

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

貢獻者指南

技術棧
java
領域
ci cddevops
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Knowledge of Jenkinsfile RunnerCustom War Packager config files
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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.