[JIRA] (JENKINS-59205) GUI doesn't display updated parameters after multiple runs

3 views

Skip to first unread message

williamsgang1@gmail.com (JIRA)

unread,

Sep 3, 2019, 10:19:04 AM9/3/19

to jenkinsc...@googlegroups.com

David Williams created an issue

Jenkins /

JENKINS-59205

GUI doesn't display updated parameters after multiple runs

Issue Type:	Bug
Assignee:	Unassigned
Components:	core
Created:	2019-09-03 14:18
Environment:	Linux 3.10.0-957.5.1.el7.x86_64 Java 1.8.0_222-b10 Jenkins 2.176.3 Plugins ace-editor 1.1 amazon-ecr 1.6 amazon-ecs 1.19 anchore-container-scanner 1.0.18 ansible 1.0 ansicolor 0.6.2 ant 1.9 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 aws-credentials 1.26 aws-java-sdk 1.11.594 aws-lambda 0.5.10 aws-parameter-store 1.2.1 basic-branch-build-strategies 1.3.2 blueocean 1.17.0 blueocean-autofavorite 1.2.3 blueocean-bitbucket-pipeline 1.17.0 blueocean-commons 1.17.0 blueocean-config 1.17.0 blueocean-core-js 1.17.0 blueocean-dashboard 1.17.0 blueocean-display-url 2.2.0 blueocean-events 1.17.0 blueocean-git-pipeline 1.17.0 blueocean-github-pipeline 1.17.0 blueocean-i18n 1.17.0 blueocean-jira 1.17.0 blueocean-jwt 1.17.0 blueocean-personalization 1.17.0 blueocean-pipeline-api-impl 1.17.0 blueocean-pipeline-editor 1.17.0 blueocean-pipeline-scm-api 1.17.0 blueocean-rest 1.17.0 blueocean-rest-impl 1.17.0 blueocean-web 1.17.0 bouncycastle-api 2.17 branch-api 2.5.2 build-timeout 1.19 cloudbees-bitbucket-branch-source 2.4.4 cloudbees-folder 6.9 command-launcher 1.3 credentials 2.3.0 credentials-binding 1.18 display-url-api 2.3.0 docker-build-publish 1.3.2 docker-commons 1.13 docker-workflow 1.17 durable-task 1.29 ec2 1.45 embeddable-build-status 2.0.2 envinject 2.1.6 envinject-api 1.5 external-monitor-job 1.7 favorite 2.3.2 file-operations 1.7 git 3.10.0 git-client 2.7.7 git-server 1.7 github 1.29.4 github-api 1.95 github-branch-source 2.5.3 golang 1.2 google-login 1.4 graphiteIntegrator 1.3-SNAPSHOT (private-06/11/2018 15:08-mitalpotey) greenballs 1.15 handlebars 1.1.1 handy-uri-templates-2-api 2.1.7-1.0 htmlpublisher 1.18 http_request 1.8.22 jackson2-api 2.9.9 javadoc 1.4 jdk-tool 1.2 jenkins-design-language 1.17.0 jira 3.0.5 job-dsl 1.76 jquery-detached 1.2.1 jsch 0.1.55 junit 1.27 ldap 1.20 lockable-resources 2.5 mailer 1.23 matrix-auth 2.4.2 matrix-project 1.14 mercurial 2.5 momentjs 1.1.1 monitoring 1.76.0 node-iterator-api 1.5.0 pam-auth 1.5.1 pipeline-aws 1.38 pipeline-build-step 2.9 pipeline-graph-analysis 1.10 pipeline-input-step 2.11 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.9 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.9 pipeline-model-extensions 1.3.9 pipeline-rest-api 2.12 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.9 pipeline-stage-view 2.12 pipeline-utility-steps 2.3.0 plain-credentials 1.5 postbuild-task 1.8 publish-over 0.22 publish-over-ssh 1.20.1 pubsub-light 1.12 resource-disposer 0.12 scm-api 2.6.3 script-security 1.62 simple-theme-plugin 0.5.1 slack 2.28 sse-gateway 1.17 ssh-agent 1.17 ssh-credentials 1.14 ssh-slaves 1.29.4 structs 1.20 timestamper 1.9 token-macro 2.8 trilead-api 1.0.3 variant 1.2 windows-slaves 1.4 workflow-aggregator 2.6 workflow-api 2.36 workflow-basic-steps 2.18 workflow-cps 2.73 workflow-cps-global-lib 2.15 workflow-durable-task-step 2.33 workflow-job 2.34 workflow-multibranch 2.21 workflow-scm-step 2.9 workflow-step-api 2.20 workflow-support 3.3 ws-cleanup 0.37
Labels:	jenkinsfile parameterized
Priority:	Minor
Reporter:	David Williams

Our Jenkinsfile's parameters have changed over time and I've noticed that old parameters are still offered in the GUI and new ones are not. This is still the case after multiple runs. We use a multi branch pipeline. New feature branches have the current parameters, but old branches like master do not.

Our Jenkinsfile pipeline is declarative with functions outside of the pipeline. I don't see any errors in the logs and I see a log message for the master branch that says Obtained Jenkinsfile from c0c0a09ae128f788139f13b9b7fc37d473dd35bf which is the correct revision. Any help would be appreciated.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)