# Properties parameters not changed after updating values

**URL:** <https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659>\
**Category:** Ask a question\
**Tags:** question, docker, pipeline\
**Created:** [July 25, 2023, 11:58am UTC](https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659 "2023-07-25T11:58:20Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![taehun.kim](https://avatars.discourse-cdn.com/v4/letter/t/bcef8e/32.png) [@taehun.kim](https://community.jenkins.io/u/taehun.kim)\
**Post date:** [July 25, 2023, 11:58am UTC](https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659/1 "2023-07-25T11:58:20Z")

</div>

Jenkins Version : 2.395

Hi, Jenkins!  
I am using Jenkins with github and created a Multibranch Pipeline job to build and test some source automatically.  
In my Jenkinsfile script(located in my github repo), I use properties parameters to give some build options such as below.

properties(  
[  
parameters([  
…  
string(defaultValue: ‘my\_build\_option’, description: ‘Build option name’, name: ‘BUILD\_OPTION\_NAME’, trim: true),  
…  
])  
]  
)

When a new branch is created inside my Multibranch Pipeline job by scanning the github repo, it works fine. But after that, when I change the properties parameters in my Jenkinsfile script, the next build executes with the previous properties parameters. This situation doesn’t change unless using ‘build with parameters’ in Dashboard \> jobs \> branches.

It only seems to work properly when a new branch is created inside the Multibranch Pipeline job for the first time.

Is there a way to apply the updated properties parameters value not using ‘build with paramters’?

Thank you.

---

<div class="post-metadata">

**Author:** ![ahmedammar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/ahmedammar/32/5057_2.png) [@ahmedammar](https://community.jenkins.io/u/ahmedammar)\
**Post date:** [July 31, 2023, 1:26pm UTC](https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659/2 "2023-07-31T13:26:30Z")

</div>

Have this same issue, any changes to `properties` on a `main` branch Jenkinsfile does not get detected. Only solution I’ve found is having to nuke the entire multi branch pipeline and re-scan the GitHub org … This is pain …

---

<div class="post-metadata">

**Author:** ![poddingue](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/poddingue/32/985_2.png) [@poddingue](https://community.jenkins.io/u/poddingue)\
**Post date:** [August 2, 2023, 7:28am UTC](https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659/3 "2023-08-02T07:28:43Z")

</div>

Hello @taehun.kim and @ahmedammar.  
Welcome to this community 👋

As far as I know, in Jenkins Multibranch Pipelines, when you make changes to the Jenkinsfile or properties parameters in your GitHub repository, those changes may not immediately take effect in the existing branches. I think this is because Jenkins caches the Jenkinsfile and other configuration files for each branch to improve performance.

To force Jenkins to re-evaluate the Jenkinsfile and pick up the changes, you could trigger a re-scan of the Multibranch Pipeline job. This should refresh the cached configuration and apply any changes made to the Jenkinsfile and properties parameters. Here’s how you could trigger a re-scan:

1. Go to the Jenkins dashboard.
2. Navigate to your Multibranch Pipeline job.
3. On the left-hand side, you’ll find a menu with options like “Status,” “Configure,” etc. Click on “Scan Repository Now.”
4. Jenkins will initiate a re-scan of your GitHub repository, and the changes made to the Jenkinsfile and properties parameters should be picked up in the subsequent builds.

---

<div class="post-metadata">

**Author:** ![ahmedammar](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/ahmedammar/32/5057_2.png) [@ahmedammar](https://community.jenkins.io/u/ahmedammar)\
**Post date:** [August 9, 2023, 11:25am UTC](https://community.jenkins.io/t/properties-parameters-not-changed-after-updating-values/8659/4 "2023-08-09T11:25:36Z")

</div>

I’ve tried this, both repo scan and org scan does not work, I have to delete the multi branch pipeline and recreate it. Seems like a bug to me.