| Currently, when a Jenkins pipeline is created, job config such as parameters, cron triggers, etc. are not populated before the first build is run. For example, when a parameter is added to a pipeline, the Jenkins UI will not allow the user to input the parameter until the job has been built with that parameter missing. In many cases this leads to a failed build, but it may cause more subtle problems depending on how the pipeline is written. This is particularly frustrating when using the seed job pattern along with Jenkins pipelines; at the moment we seed our jenkins jobs nightly to ensure that our Jenkins configuration doesn't drift from source controlled job definitions. Every time a parametrized Pipeline job is seeded, the first run after the seed will not accept parameters and fail, forcing us to re-run the job. Functionality should be available to force jenkins to pull the latest Pipeline script and update job configuration in line with that script without running a build. This would allow us to trigger this "config refresh" from our seed job and avoid confusing and disruptive build failures. |
