On Thu, Nov 13, 2014 at 4:17 PM, Daniel Beck wrote:
> So it behaves correctly. The label part is only part of the sub-builds (where
> the project name has the suffix with the active axis values), not the overall
> build (which does not), and if the trigger is run once for the overall build,
>
On Fri, Nov 7, 2014 at 7:17 AM, Daniel Beck wrote:
> Is the downstream build triggered for every matrix axis that finishes
> building, or only once, when all axes finished?
Sorry for the delay I've been busy with getting a release out of the door.
The downstream build is triggered when all axes
On Thu, Nov 6, 2014 at 4:15 PM, Ginga, Dick wrote:
> Change the jobname to labl:sl6? Or labl-sl6?
I can't, that's what Jenkins assigns. The job itself is called LAL and
the matrix plugin adds /label=sl6, /label=wheezy, etc... depending on
which operating system I'm trying to build on. I build the
On Thu, Nov 6, 2014 at 7:15 AM, Ginga, Dick wrote:
> Perhaps the label=sl6 is getting parsed as another parameter?? Try \'ing it:
> label\=sl6
Interesting idea, that kind of makes sense. The problem is that
there's nothing for me to escape, as label=sl6 is part of JOB_NAME
itself.
Cheers
Adam
On Wed, Nov 5, 2014 at 4:30 PM, Dunnigan, Terrence J
wrote:
> Are you using a recent version of Jenkins and the parameterized plugin?
The current LTS release and the latest parameterized plugin, at least
Jenkins tells me that no updates are available for my plugins.
> I suspect the problem is t
Hi
According to the documentation for the Parameterized Trigger plugin,
specifically for 'Predefined parameters":
"""
KEY=value pairs, one per line (Java properties file format).
Backslashes are used for escaping, so use "\\" for a single backslash.
Current build parameters and/or environment va
Hi
I've upgraded my test Jenkins instance to 1.580.1, to validate before
upgrading my production instance, and since doing so the matrix plugin
doesn't seem to be working correctly. When selecting nodes/labels to
build in the Configuration Matrix there doesn't seem to be any match
between label an
I'm still seeing this. Any ideas?
Cheers
Adam
On Tue, Oct 28, 2014 at 7:50 AM, Adam Mercer wrote:
> Hi
>
> I was trying to view a failed test log from the workspace of a project
> this morning and I received the following stack trace:
>
> java.io.IOException: Remot
On Thu, Oct 30, 2014 at 1:31 PM, Ross Aribi wrote:
> You have two jobs, Job1 calling Job2. The parameter $JOB_NAME is local to
> each job, so in Job2 the value of $JOB_NAME is Job2.
> Add an additional param in Job1 ($JOB_1_NAME=$JOB_NAME) and use it in Job2.
That's exactly what I'm doing, these
On Thu, Oct 30, 2014 at 11:56 AM, T. Anthony Rabaa wrote:
> If you're building on the same node, why not pass in the full path to the
> libraries as a parameter?
Good idea. I'll give that a go.
Cheers
Adam
--
You received this message because you are subscribed to the Google Groups
"Jenkins
Hi
I was trying to view a failed test log from the workspace of a project
this morning and I received the following stack trace:
java.io.IOException: Remote call on builder-sl6-1 failed
at hudson.remoting.Channel.call(Channel.java:751)
at hudson.FilePath.act(FilePath.java:1009)
at jenkins.util.Vi
Hi
Anyone? Surely the plugin shouldn't be stripping information when
passing it on to downstream jobs?
Cheers
Adam
On Thu, Oct 23, 2014 at 5:15 PM, Adam Mercer wrote:
> Hi
>
> I'm trying to tie a couple of jobs together using the Parametrized
> Trigger Plugin and am runn
Hi
Hi
I'm trying to tie a couple of jobs together using the Parametrized
Trigger Plugin and am running into problems with the second job
finding the libraries built by the first job.
When the first job completes successfully I trigger a build of the
second job, I'm forcing it to use the same nod
On Tue, Aug 19, 2014 at 8:18 AM, Ginga, Dick wrote:
> The Parameterized Trigger plugin lets you trigger one job from another and
> pass to that job a set of parameters. You can use the $BUILD_NUMBER and
> $JOB_NAME as parameters.
Thanks, that seems to be useful.
> There is also the Build Flow
Can anyone offer any help regarding this? Or point to some useful
documentation as the plugin documentation is not much help?
Cheers
Adam
On Thu, Aug 14, 2014 at 3:21 PM, Adam Mercer wrote:
> Hi
>
> I'm trying to use the Multijob plugin write a series of jobs for
> building a
Hi
I'm trying to use the Multijob plugin write a series of jobs for
building a connected series of libraries. How can I pass appropriate
metadata from one project to subsequent projects. For example the
BUILD_NUMBER and the JOB_NAME?
Or is the Multijob plugin not the best way to achieve this?
Ch
Hi
Managed to figure this out, turns out the server running Jenkins ran
into a file system problem and the root filesystem was remounted
read-only. FIxing the file system problem got things running again.
Cheers
Adam
On Sun, Jul 6, 2014 at 11:00 AM, Adam Mercer wrote:
> Hi
>
> Thi
Hi
This morning one of my builds slaves was reporting that both it's
executors were Dead and reported traces such as:
java.io.IOException: Failed to create a temporary file in
/var/lib/jenkins/jobs/PyLAL_Epydoc
at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:67)
at hudson.util.AtomicFileWr
On Wed, Mar 5, 2014 at 5:20 PM, Daniel Beck wrote:
> If there are many directory entries in the particular directory you're
> viewing, likely because of JENKINS-21780:
> https://issues.jenkins-ci.org/browse/JENKINS-21780
That sounds like it. Thanks.
Cheers
Adam
--
You received this message b
On Wed, Mar 5, 2014 at 1:19 PM, Daniel Beck wrote:
> You're running Jenkins behind a reverse proxy (Apache, nginx, ...) and
> Jenkins takes so long to respond that the proxy gives up.
>
> Increase the timeout.
But why is it taking so long? The machine which is workspace is on is
contented via a
Hi
Access to a jobs workspace has always been slow for me but this
morning it's timing out and I'm getting an error of the following form
when trying to view the workspace:
"""
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle th
xecutors.
>>
>> Is there another way you can think of for achieving this . If you could
>> throw some light on how you arrived at the workaround, it might help me to
>> figure out a solution for my case.
>>
>> Thanks,
>>
>> Neetish.
>>
>>
>>
>&g
On Mon, Feb 18, 2013 at 11:32 AM, Christoph Kutzinski wrote:
> That is an issue with the Git and the CVS plugin.
> You can work around by disabling the CVS plugin.
Thanks, good job none of my projects are using CVS.
Cheers
Adam
--
You received this message because you are subscribed to the Go
On Mon, Feb 18, 2013 at 9:53 AM, wrote:
> The latest Git plugin says:
> Version 1.1.28 (February 17, 2013)
> fix a regression that breaks jenkins remoting
Thanks, that was it, 1.1.28 works without issue.
Cheers
Adam
--
You received this message because you are subscribed to the Google Gr
On Mon, Feb 18, 2013 at 8:49 AM, Marek Gimza wrote:
> We had the same problem.
> After reading through some of the blogs and tickets, we deduced the
> problem to be in the compatibility of the Java JRE on the slave and
> master.
Interesting...
> Try checking the versions of the JAVA that runs th
Hi
All of a sudden all my builds have started failing with errors of the form:
Started by user admin
Building remotely on SL6a in workspace /var/lib/jenkins/jenkins/lalsuite_ci
Checkout:lalsuite_ci / /var/lib/jenkins/jenkins/lalsuite_ci -
hudson.remoting.Channel@5e5edf72:SL6a
Using strategy: Defa
On Tue, Feb 12, 2013 at 4:13 PM, Adam Mercer wrote:
> Thanks, that's what was confusing me. I've adjusted the priorities
> according and I'll see how that effects the behaviour.
And that did the trick, jobs are now running with the priority I expect. Thanks!
Cheers
Adam
On Tue, Feb 12, 2013 at 4:07 PM, J Arrizza wrote:
> And one last bit of confusion that still manages to bite me: the higher the
> priority number, the higher the priority. For some reason, I think #1 is
> the highest priority... it isn't, it's the lowest. So your job priority of
> 10 is low comp
On Tue, Feb 12, 2013 at 3:45 PM, Merrow, Frank wrote:
> Yep . . . . . .
>
> All I know is if I want to temporally boost the priority of a job without
> losing what the original value "was" . . . I add a zero on the end, save and
> it jumps to the front of the queue. At a later time I can come
On Tue, Feb 12, 2013 at 3:26 PM, Merrow, Frank wrote:
> The priority for this job. Priorities are used when all executors are busy
> to decide which job in the build queue to run next. A job with higher
> priority is ran before jobs with lower priorities.
>
> So the job you want to run first shou
On Tue, Feb 12, 2013 at 3:21 PM, Mandeville, Rob wrote:
> Check the open issues list on that plugin. It looks like jobs kicked off by
> hand (rather than scheduled automatically) ignore priority sorting. Someone
> listed that as a feature there. If you kicked off the priority 10 job by
> han
Hi
I'm using the Priority Sorter Plugin[1] as I'd like one project to use
the next available build host regardless of the other jobs ahead of it
in the queue. According to the documentation for the plugin:
"This plugin allows jobs waiting in the build queue to be sorted by a
static priority rathe
On Mon, Jan 28, 2013 at 9:00 PM, Adam Mercer wrote:
> That sounds like a reasonable explanation. Is there a way I can have a
> separate workspace for polling, so that this doesn't block?
Just to close the loop on this, I set a custom workspace for this
project and this allowed multi
On Mon, Jan 28, 2013 at 6:25 PM, cjo wrote:
> Try adding a logger for hudson.slaves.WorkspaceList to the log page and see
> if there is a log message
> " acquired "
> occurring just after the first build finishes, which would indicate that
> this is the case.
Sorry but I'm very new to Jenkins,
Hi
One of my Jenkins projects is configured to poll git and trigger a new
build if appropriate by using a post-receive hook and the Git Plugin.
This specific project has two build slaves which can build the project
but it seems that if a single build is already in progress, with one
slave idle, a
On Mon, Jan 21, 2013 at 7:39 PM, Mark Waite wrote:
> With the version of curl I'm using (7.26.0 - as delivered with Debian
> "Wheezy"), I can use the arguments -o /dev/null to prevent that output.
> Does that not work for you?
The git server has curl-7.15.5 and I thought I'd already tried that
op
On Mon, Jan 21, 2013 at 5:38 PM, Adam Mercer wrote:
> this seems to be working great, i.e. a new build is scheduled if
> appropriate. However the post-receive hook outputs:
>
> Scheduled polling of Project
An example is:
$ git push
Counting objects: 9, done.
Delta compression u
Hi
I'm using the git plugin and trying to write a post-receive hook to
trigger polling of the SCM to see if a new build should be triggered.
I'm using the following to get Jenkins to poll the SCM
/usr/bin/curl $JENKINS/git/notifyCommit?url=$REPO&branches=master
this seems to be working great, i.
On Mon, Jan 21, 2013 at 12:30 AM, Slide wrote:
> I don't think its possible to do this.
Thanks, I'm already up to 30+ users and it's only been a few days. I
guess it's just something I'll have to live with.
Cheers
Adam
Anyone?
On Wed, Jan 16, 2013 at 9:08 PM, Adam Mercer wrote:
> Hi
>
> I set up a test installation of Jenkins today and I've noticed that it
> seems to auto create users based on new commits in the repository. I
> know these aren't full user accounts and can't be use
Hi
I set up a test installation of Jenkins today and I've noticed that it
seems to auto create users based on new commits in the repository. I
know these aren't full user accounts and can't be used to log into the
system but is there a way to disable the creation of these accounts.
The software I
41 matches
Mail list logo
