UMBER%"
> > "http://user:password@localhost
> :8080/job/SUB_JOB2/nextbuildnumber/submit"
> >
> >
> >
> > Chris Williams
> >
> > Dell | PG Release Engineering
> >
> >
> >
> >
> >
> > From: jenkinsci-users@google
ams
>
> Dell | PG Release Engineering
>
>
>
>
>
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of djx339
>
> Sent: Wednesday, June 26, 2013 12:18 PM
>
> To: jenkinsci-users
>
> Subject: Re: Re: How to use t
tbuildnumber/submit";
Chris Williams
Dell | PG Release Engineering
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of djx339
Sent: Wednesday, June 26, 2013 12:18 PM
To: jenkinsci-users
Subject: Re: Re: How to use the same BUILD_NUM in two differe
thanks
From: Benjamin Lau
Date: 2013-06-27 01:16
To: jenkinsci-users
Subject: Re: Re: How to use the same BUILD_NUM in two different jobs?
Next Build Number
https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin
On Jun 26, 2013 1:06 PM, "djx339" wrote:
can you tell me
Next Build Number
https://wiki.jenkins-ci.org/display/JENKINS/Next+Build+Number+Plugin
On Jun 26, 2013 1:06 PM, "djx339" wrote:
> **
> can you tell me the plugin name? thanks
>
>
> *From:* Benjamin Lau
> *Date:* 2013-06-27 01:02
> *To:* jenkinsci-users
>
can you tell me the plugin name? thanks
From: Benjamin Lau
Date: 2013-06-27 01:02
To: jenkinsci-users
Subject: Re: How to use the same BUILD_NUM in two different jobs?
You don't want to do this. It's an extremely good practice to make sure that
all build numbers are unique.
But if y
You don't want to do this. It's an extremely good practice to make sure
that all build numbers are unique.
But if you want to do this anyway... I think there's a plugin which let's
you explicitly set the build number. I use it to jump the build number up
when I make major backward incompatible ch
i have an branch in git repository to fix bug, and coding new features in
master branch.
my job1 is for branch build to verify bug. job2 is for master build.
i should change the version in every job. and the version is job's
BUILD_NUM.
so i should use one BUILD_NUM between two jobs.
hao can i do?
Your questions seems a bit confusing. Are you asking how you can make it so
that the jobs are the same build number?
Or are you asking how you could make it so that job2 is always 1 build number
higher than job1?
- Original Message -
From: djx...@gmail.com
To: jenkinsci-user
