Jenkins never wraps build numbers, so something has gone badly wrong.
The number of the next build for each job is stored in file
${JENKINS_HOME}/jobs/jobname/nextBuildNumber, with the actual build results
in ${JENKINS_HOME}/jobs/jobname/builds/. You might want to see if that
directory was
To: jenkinsci-users@googlegroups.com
Sent: Thursday, May 29, 2014 3:48:35 AM
Subject: RE: a few Jenkins questions
Jenkins never wraps build numbers, so something has gone badly wrong.
The number of the next build for each job is stored in file
${JENKINS_HOME}/jobs/jobname
On 29.05.2014, at 13:37, wak...@comcast.net wrote:
would be a build number reset at some point ?
Well, it's an int. After build number 2.147.483.647 it wraps around to
-2.147.483.648 and Jenkins basically breaks, failing to show these builds on
the UI.
Not sure this is a relevant limitation
build
set up when we're ready to Release.
anyways, thanks to Matthew and Daniel for the support.
- Original Message -
From: Daniel Beck m...@beckweb.net
To: jenkinsci-users@googlegroups.com
Sent: Thursday, May 29, 2014 8:30:32 AM
Subject: Re: a few Jenkins questions
On 29.05.2014
Given that the timing loops in jenkins put a lower bound of 100ms or so
before a build starts, unless you have a very large executor pool and
enable concurrent execution I suspect that the build numbers will be safe
for us from overflow... unless somebody finds a fountain of youth!
On 29 May
: a few Jenkins questions
On 29.05.2014, at 13:37, wak...@comcast.net wrote:
would be a build number reset at some point ?
Well, it's an int. After build number 2.147.483.647 it wraps around to -
2.147.483.648 and Jenkins basically breaks, failing to show these builds
on the UI.
Not sure
