# Jenkins plugin release build number is adding -rc **URL:** \ **Category:** Ask a question\ **Tags:** question, pipeline\ **Created:** [July 29, 2024, 9:35am UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615 "2024-07-29T09:35:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Mun](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@Mun](https://community.jenkins.io/u/Mun)\ **Post date:** [July 29, 2024, 9:35am UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/1 "2024-07-29T09:35:41Z")
Hi, We raised pull request in Jenkins with respect to our final code changes and while creating the build number it is adding -rc and all number as a suffix. Till 4.0.7 version it is creating build number perfectly fine but from 4.0.8 onwards, it is adding -rc below is the release link [Leapwork | Jenkins plugin](https://plugins.jenkins.io/leapwork/releases/) ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/f/fcd6547f325fb1f8c0e159a54885e60baf1c4b18.png) below is the code repo link [GitHub - jenkinsci/leapwork-plugin: Leapwork Integration with Jenkins](https://github.com/jenkinsci/leapwork-plugin) Kindly assist ---
**Author:** ![Mun](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@Mun](https://community.jenkins.io/u/Mun)\ **Post date:** [July 29, 2024, 9:36am UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/2 "2024-07-29T09:36:26Z")
@mawinter69 Kindly assist if you can share some insights about this ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [July 29, 2024, 12:10pm UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/3 "2024-07-29T12:10:38Z")
I’ve submitted a pull request that proposes the necessary change and includes a detailed description explaining why the change is needed. > > > \## Set changelist.format for automated releases > > The \["Automated release" docume…ntation\](https://www.jenkins.io/doc/developer/publishing/releasing-cd/) includes a section that describes the automated release configuration used in this repository. The section is "Manually controlled prefix (optional)" and it includes instructions that the .mvn/maven.config file must include the line: > > \`\`\` > \-Dchangelist.format=%d.v%s > \`\`\` > > The .mvn/maven.config in the repository does not include that line, so Maven is using the default value of the changelist.format. > > A little earlier in that page, it includes the instructions so that a developer can check the version number pattern that they have selected. The commands to check that are: > > \`\`\` > mvn validate > mvn validate -Dset.changelist -Dignore.dirt > \`\`\` > > When I run \`mvn validate\` on this repository before this change, one of the output lines is: > > \`\`\` > \[INFO\] Building Leapwork 4.0.12-SNAPSHOT > \`\`\` > > When I run \`mvn validate -Dset.changelist -Dignore.dirt\` on this repository before this change, one of the output lines is: > > \`\`\` > \[INFO\] Building Leapwork 4.0.12-rc93.784bbceeef27 > \`\`\` > > That output is because the \`changelist.format\` is not set in the .mvn/maven.config file. > > After I added the \`changelist.format\`, the output is now: > > \`\`\` > \[INFO\] Building Leapwork 4.0.12-93.v784bbceeef27 > \`\`\` > > \### Testing done > > Confirmed that \`mvn validate\` output has expected format with changes and that it has the undesired format before this change. > > \### Submitter checklist > \- \[x\] Make sure you are opening from a \*\*topic/feature/bugfix branch\*\* (right side) and not your main branch! > \- \[x\] Ensure that the pull request title represents the desired changelog entry > \- \[x\] Please describe what you did > \- \[x\] Link to relevant issues in GitHub or Jira > \- \[x\] Link to relevant pull requests, esp. upstream and downstream changes > \- \[x\] Ensure you have provided tests - that demonstrates feature works or fixes the issue For reference, the explanation in that pull request includes: The [“Automated release” documentation](https://www.jenkins.io/doc/developer/publishing/releasing-cd/) includes a section that describes the automated release configuration used in this repository. The section is “Manually controlled prefix (optional)” and it includes instructions that the .mvn/maven.config file must include the line: ```auto -Dchangelist.format=%d.v%s ``` The .mvn/maven.config in the repository does not include that line, so Maven is using the default value of the changelist.format. A little earlier in that page, it includes the instructions so that a developer can check the version number pattern that they have selected. The commands to check that are: ```auto mvn validate mvn validate -Dset.changelist -Dignore.dirt ``` When I run `mvn validate` on this repository before this change, one of the output lines is: ```auto [INFO] Building Leapwork 4.0.12-SNAPSHOT ``` When I run `mvn validate -Dset.changelist -Dignore.dirt` on this repository before this change, one of the output lines is: ```auto [INFO] Building Leapwork 4.0.12-rc93.784bbceeef27 ``` That output is because the `changelist.format` is not set in the .mvn/maven.config file. After I added the `changelist.format`, the output is now: ```auto [INFO] Building Leapwork 4.0.12-93.v784bbceeef27 ``` ---
**Author:** ![Mun](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@Mun](https://community.jenkins.io/u/Mun)\ **Post date:** [July 29, 2024, 1:58pm UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/4 "2024-07-29T13:58:33Z")
Thank you !! it is working fine as expected locally. Once I will raise pull request at jenkins, hope it will work there too. ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [July 29, 2024, 2:29pm UTC](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/5 "2024-07-29T14:29:21Z")
> [@Mun](#): > > it is working fine as expected locally The [description](https://community.jenkins.io/t/jenkins-plugin-release-build-number-is-adding-rc/17615/3) explains why it works locally for you. Local development does not use the flag to set the changelist, (`-Dset.changelist`) so you won’t see it locally unless you include that argument in your Apache Maven command line.