ok, got it:
b = build( my-build )
out.println b.build.properties.environment['SVN_REVISION']
Thank you for your reply. Now I have some reading.
Preferably UI, but if I can do it programmatically it's ok.
On Thu, Aug 9, 2012 at 12:06 PM, Michaël Pailloncy mpapo@gmail.com wrote:
A similar subject has been create :
Hi,
I am generating/changing lots of regression test jobs via groovy to
keep our build machines chewing during the night. Yesterday I had to
change some parameters in our jobs but the existing cron section
stayed the same. When diffing the config file it shows my changes, the
trigger section
Hello,
I have this problem for the longest time but never got around to fixing it
until recently.
I am running jenkins on winstone with java wrapper.
In my wrapper.conf, we have set 8070 as the http port that our jenkins
instance listens to.
When starting or restarting my jenkins instance
Thanks! Worked perfect!
On Thu, Aug 9, 2012 at 7:55 PM, Christopher Orr ch...@orr.me.uk wrote:
Hi there,
On 08/09/2012 09:33 PM, Brant Boehmann wrote:
I am using the publish over ssh plugin. I have roughly 100 different
servers configured for various applications to get automatically
1. There is a single executor running on the machine. There is no issue
with multiple powershell sessions at the same time. It just creates a new
powershell process.
2.That path exists even when the script fails.
3. There isn't anything in the script that returns 2. The way that I
structure my
Is it possible to just delete the build? I've seen builds from other jobs show
up in a different job's list and since the build number was much higher it hid
the test failures in the real build because it was the lastSuccessfulBuild due
to the build number being so big. I solved that problem
On Thu, 09 Aug 2012, de Herdt Arne wrote:
Hello,
I'm currently in the process of setting up a Jenkins instance on Debian to
have our team play around and see how we can work with Jenkins.
I have configured a Ruby plan that is able to checkout the source from our
git, the problem is
The weird thing is that all slaves were still working and I could build
other jobs, so if it's memory related issue, then it might affect that
particular phantom build.
The other problem is on identifying which slave is having the problem. I
checked the logs of each one, and didn't find any error.
Do you mean kill the build by deleting something directly on the filesystem?
I tried stopping the build (the red x icon next to the progress bar), but
it didn't do anything, phantom build kept going.
I wonder what's causing the job to think that there's a build running (job
page showing a running
ERROR: Processing failed due to a bug in the code. Please report this to
jenkinsci-us...@googlegroups.comjava.lang.NullPointerException
http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException
at hudson.model.listeners.RunListener.all(RunListener.java:216)
11 matches
Mail list logo
