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
Well, content-type had to be form-www-urlencoded...
On Wednesday, May 28, 2014 11:47:48 PM UTC-4, Vinicius Carvalho wrote:
Jenkins version: 1.565
Github plugin version : 1.8
github authentication plugin: 0.16
Hi there, I'm trying to get the webhooks plugin to work, but after a few
hours I
thanks for the quick reply. So, the build numbers just keep increasing forever
?? I would think that there
would be a build number reset at some point ?
I will take a look given the info you provided below.
-wk
- Original Message -
From: Matthew Webber matthew.web...@diamond.ac.uk
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
beyond the expected java int issues, I would think that when folks talk about
build numbers, they don't talk in
the thousands..perhaps its just me ? We are in the development stages at the
moment and builds are happening
quite often, thus the numbers can get pretty high. I'll have a different
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
I have a simple build flow with the following statements which just print
out the environment variables.
out.println 'Build Object Properties:'
build.properties.each { out.println $it.key - $it.value }
A email-ext post build action with a trigger of always has been setup. The
recipient is
Can you post the console output?
On Thu, May 29, 2014 at 11:13 AM, Mark Sherman msher...@gogii.net wrote:
I have a simple build flow with the following statements which just print
out the environment variables.
out.println 'Build Object Properties:'
build.properties.each { out.println
I am trying to switch to Jenkins from CCnet, single builds work flawlessly
, but we have heavy project dependancies and I'm not sure what is the
Jenkin's way to resolve them.
We have low level project that builds dlls we use in other projects so I
need somehow to commit that project build
I'm trying to build a selectable subversion branch. When I select the
branch from the dropdown, and kick off the build it fails because it hasn't
actually pulled the code from svn and so the workspace is empty.
This seems like the simplest use case, so I don't understand why it doesn't
work.
We are trying to set up a multi-configuration job in Jenkins with a
user-defined axis that will set multiple parameters in the job. For
example, we need to have a value called $name and a value called $url set
in each build, like the following:
$name, $url
URL A, www.some-url.com/thing-a
URL
That parameter is provided by the Subversion plugin.
It simply allows you to select a branch (or tag, or any folder really) from
Subversion as job argument. It doesn't check it out, that's what selecting the
Subversion SCM further down in the job config is for. A bit like the Choice
Parameter,
Call them 'A', 'B', and 'C', and derive the Name and URL from that in your
build script. Clearly they're not independent axes.
On 29.05.2014, at 22:23, Trey Duskin t...@starmobileinc.com wrote:
We are trying to set up a multi-configuration job in Jenkins with a
user-defined axis that will
when folks talk about build numbers, they don't talk in the thousands..
A sampling of some of our more frequent current builds shows that we have
few builds that are NOT in the thousands. The highest one is on build
number 31751 right now. That's the only one above 10,000, though.
Another thing
Thanks for the snappy reply.
Works great!
Thanks again.
On Thu, May 29, 2014 at 3:03 PM, Daniel Beck m...@beckweb.net wrote:
That parameter is provided by the Subversion plugin.
It simply allows you to select a branch (or tag, or any folder really)
from Subversion as job argument. It
Hi All
When we run my python script in the shell terminal, it works
sudo myscript.py --version=22 --base=252
--hosts={'hostA':[1],'hostB':[22]}
But when we run in Hudson and Jenkins, using Execute Shell step, somehow,
the string --hosts={'hostA':[1],'hostB':[22]} is interpreted as
sudo
Thanks for your help.
I simplified the DSL command for the flow to:
out.println 'Build Object Properties:'
This is the console output:
Started by user msherman http://masterbuild.gogii.net:8080/user/msherman
Build Object Properties:
Finished: SUCCESS
The email
17 matches
Mail list logo
