As huybrechts seems to be away doing other stuff,
Can some one look at the 12 Pull requests on the
parameterized-trigger-plugin.
https://github.com/jenkinsci/parameterized-trigger-plugin/pulls
I will merge these into the master and make a release but seeing as many of
these requests are mine,
On Thursday, January 24, 2013 5:56:33 PM UTC+1, Jesse Glick wrote:
On 01/24/2013 08:21 AM, lvot...@redhat.com javascript: wrote:
Revert commit
I would say revert (bdaf5ea too); at least I do not see a clear
description in #494 as to the original purpose of the change.
Note that the
Hi again,
I patched out jenkins using the following code snippet
in AbstractMavenProcessFactory#buildMavenAgentCmdLine(...)
JDK jdk = getJava(listener);
if(jdk==null) {
// ffromm, 2013-02-17: get JAVA_HOME from envVars
if(envVars.containsKey(JAVA_HOME)) {
I'm trying to use the jenkins api (http://javadoc.jenkins-ci.org/*) *to
abort a running build however I can't seem to figure it out. Any help would
be appreciated.
My specific use case is to lookup a particular build that contains a
parameter value (id) and if the id matches I want to abort
On 01/25/2013 09:31 AM, Jerome Lacoste wrote:
the modified method shouldn't be used for encoding query params
Then it would be better to introduce a new method.
The only place I know ampersand can be a problem in URLs on the command line is
when the URLs are not quoted.
That is a user
On 01/25/2013 02:13 PM, Vojtech Juranek wrote:
The only one I don't understand is
JENKINS-16341 and 08efdf5d3ab9
- does replacement of Set by Array reduce memory footprint in any substantial
way?
No, the point is the calls to intern(), since a lot of the copied objects are common String’s.
Hi,
I have a puzzling problem related to the jenkins perforce plugin.
Up to now I have thought that plugins only dervive configuration data
from the main config.xml file for each job.
But I am seeing evidence of plugin configuration data being persisted
that survives a reboot.
Is it even
Hi Folks,
I am writing a custom BuildWrapper, which is configurable via the
Configure option on a job. This contains a repeatable section, which has
two principle inputs ; a name, and a day of the week.
The jelly looks something like this:
f:entry title=${%Allocation:}
On 01/25/2013 03:04 PM, Russ Tremain wrote:
I have thought that plugins only dervive configuration data from the main
config.xml file for each job.
Some plugins use additional global configuration files. Not sure offhand if
that is true for the Perforce plugin.
OK, so i got there in the end - but I've had to manually bind the fields in
the same entry:
f:entry title=${%Days}
f:checkbox checked=${instance.monday==true} name=monday
title=Monday /
f:checkbox checked=${instance.tuesday==true} name=tuesday
OK, so I really was being stupid... Dind't try the obvious
f:entry title=${%Days}
f:checkbox field=monday title=Monday /
f:checkbox field=tuesday title=Tuesday /
f:checkbox field=wednesday title=Wednesday /
f:checkbox field=thursday
At 4:33 PM -0500 1/25/13, Jesse Glick wrote:
On 01/25/2013 03:04 PM, Russ Tremain wrote:
I have thought that plugins only derive configuration data from the main
config.xml file for each job.
Some plugins use additional global configuration files. Not sure offhand if
that is true for the
Hi,
I'd like to request hosting for my new Jenkins uptime plugin. It displays
the percentage of time that a job has been building successfully over its
lifetime.
It is currently at:
https://github.com/chrismair/uptime-plugin
Thanks.
Chris Mair
13 matches
Mail list logo
