if the goal is to convience them i think you should go an explain them why
this is better, both this single difference but also why they should love
Jenkins and be glad that they had CruiseControl up until now
2013/9/5 Edwin Castro <0ptikgh...@gmx.us>
> On 9/5/13 7:25 AM, Volodymyr Kostyrko wro
Thanks for the information. I will take a look at the plugin and see if we
can take advantage of it somehow. Otherwise, I will see if I can impose
this change on my group without too much uproar.
Peter
On Thursday, September 5, 2013 9:25:57 AM UTC-5, Volodymyr Kostyrko wrote:
>
> 05.09.2013 1
On 9/5/13 7:25 AM, Volodymyr Kostyrko wrote:
> If you need to count "good" build maybe you need to look at Version
> Number Plug-In?
> (https://wiki.jenkins-ci.org/display/JENKINS/Version+Number+Plugin) It
> can create your own $VERSION based on how many successful builds were
> in total, today or
05.09.2013 16:36, peterman1002 wrote:
Hello,
I am new to Jenkins and trying to setup my build environment. I have
noticed that when a build fails, the build number is still incremented.
How can I prevent Jenkins from doing this? I'm not here to start a
debate on whether that is the correct beh
>> But if you really what to do this, i think it can be done by hacking the
>> file placed
>> $hudson/jobs//nextBuildNumber in the end of you build if you now
>> it failed,
Don’t do that. Jenkins code assumes that the number increases with each run
(pass or fail). If you invalidate that assumpt
I will see if I can convince my group that this behavior is intended and
see if they can live with it. I am just sick of the old Cruise Control
application that hasn't been updated in like 5 years.
Peter
On Thursday, September 5, 2013 9:12:46 AM UTC-5, matthew...@diamond.ac.uk
wrote:
>
> >> B
Thank you for your replies. We are trying to migrate from Cruise Control,
so there a build failure did not receive a build number. I am trying to
mimic some Cruise Control behavior to help convince my group to migrate.
If too many things are different, I don't think I will get approval.
Pete
I must claim that i think you are going in the wrong direction.
But if you really what to do this, i think it can be done by hacking the
file placed $hudson/jobs//nextBuildNumber in the end of you build
if you now it failed, this would probably work best if implemented in
groovy where you have acc
You can't. At least, you can't reuse the same job number for a later build
because the job number uniquely identifies the results of that job and is
used to store the results of that job in the file system.
If you want a monotonically increasing number which only increases when you
successfull
Hello,
I am new to Jenkins and trying to setup my build environment. I have
noticed that when a build fails, the build number is still incremented.
How can I prevent Jenkins from doing this? I'm not here to start a debate
on whether that is the correct behavior or not. I just want to know h
10 matches
Mail list logo
