OK then let's go back to your original question. You say you"need to bump version numbers". I would guess this is actually not the root reason.
Why do you want to do that? I mean: if they are different jobs, so probably for different things, why would want to do that? It does indeed seem surprising to me at first sight. Le 17 oct. 2016 4:28 PM, "Guy Matz" <[email protected]> a écrit : > Yeah, sorry, I'm not actually suggesting bumping version #s is the way to > go . . . I was hoping that maybe I was approaching the problem the wrong > way, and that someone had a better idea. Thanks!! > > On Mon, Oct 17, 2016 at 10:00 AM, 'Björn Pedersen' via Jenkins Users < > [email protected]> wrote: > >> Hi, >> >> It could be done, but think about using a better versioning scheme. >> Using build numbers from different jobs seems like a way to ask for >> trouble. >> >> Take a look at: >> https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin >> https://wiki.jenkins-ci.org/display/JENKINS/semantic-versioning-plugin >> https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin >> >> Björn >> >> >> Am Montag, 17. Oktober 2016 15:44:25 UTC+2 schrieb Guy Matz: >>> >>> Hello! I need to be able to bump version numbers between two different >>> jobs, meaning that if job A runs, it should have a build number higher that >>> job B, and if job B runs, it should have a build # higher than job A . . . >>> for example, job A may run 10 ten times and have a build number of 10. >>> Then job B will run and needs a build # of 11. Job A wight run after than >>> and needs a build # of 12. >>> >>> Anyone know how to do this? I *think* I need this because I am going to >>> have parallel tracks in my SDLC: my usual develop -> master and a new >>> hotfix -> master SDLC being build by a separate job. Do I need this? Any >>> better ideas out there? This seems like a common enough problem that it's >>> already been solved six ways to sunday . . . >>> >>> Thanks a lot, >>> Guy >>> >> -- >> 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 [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/jenkinsci-users/ff35676e-c537-493d-ab45-62a5ce42ca8f% >> 40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-users/ff35676e-c537-493d-ab45-62a5ce42ca8f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/CABnTgtWcTbM%2B4UKXifEmAo1TWDZr8jWny9W% > 2BgJ817iFpgvhg3A%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-users/CABnTgtWcTbM%2B4UKXifEmAo1TWDZr8jWny9W%2BgJ817iFpgvhg3A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS66KV34yQXdUGxTBKHbH3d4WK1vGRo36PPpMhjPO87qzg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
