Multibranch pipeline global build number

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Multibranch pipeline global build number

kubetest499
Each branch built starts with build #1 which doesn't help when you're building docker images based upon your version e.g. 1.0.1-build_number...

develop branch could be 1.0.1-1
and release branch could also be 1.0.1-1

Is there any way to have globally incremental build numbers using the multibranch pipeline?

Thanks

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/00688e1c-9316-461f-9248-16003b56d59d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch pipeline global build number

Matt-4
Hi Kubet, did you find a solution to this issue? We also have this problem which could be quite dangerous...


On Wednesday, May 24, 2017 at 4:34:36 PM UTC+1, [hidden email] wrote:
Each branch built starts with build #1 which doesn't help when you're building docker images based upon your version e.g. 1.0.1-build_number...

develop branch could be 1.0.1-1
and release branch could also be 1.0.1-1

Is there any way to have globally incremental build numbers using the multibranch pipeline?

Thanks

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/40bc627a-cdd9-4e26-844a-15a88ac2d351%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch pipeline global build number

Daniel Beck

> On 24. Jan 2018, at 13:21, Matt <[hidden email]> wrote:
>
> We also have this problem which could be quite dangerous...

Include the branch name and/or PR number in the version number string; perhaps unless it's master (or whatever you usually release from).

Safe and unambiguous.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2610FDBF-EE5D-4F93-8C43-3C9A5C07B10C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Multibranch pipeline global build number

Victor Martinez
In reply to this post by Matt-4
I don't know if IIUC, but here my quick though, what if you set the build name with those details as explained here:
- https://support.cloudbees.com/hc/en-us/articles/220860347-How-to-set-build-name-in-Pipeline-job

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6f07983e-37fc-4dd5-a8c0-a323e1b361b8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.