Re: Multibranch pipeline global build number

[Victor Martinez]

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 jenkinsci-users+unsubscr...@googlegroups.com.
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.

Re: Multibranch pipeline global build number

[Daniel Beck]

> On 24. Jan 2018, at 13:21, Matt  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 jenkinsci-users+unsubscr...@googlegroups.com.
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.