Essentially,
this:
http://stackoverflow.com/questions/32704360/how-can-i-trigger-a-jenkins-job-upon-completion-of-a-set-of-other-jobs#
I know about the multijob plugin and I know about the workflow plugin. Both
are useless, as they only allow me to schedule static "phases", which turn
out to b
Thanks, that seems to work...
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://gro
; On 09.05.2014, at 21:40, Christian Goetze
> >
> wrote:
>
> > I just filed https://issues.jenkins-ci.org/browse/JENKINS-22954
> >
> > It appears that if I change the node label string via groovy, that
> change is not immediately effective, even if I save the
I just filed https://issues.jenkins-ci.org/browse/JENKINS-22954
It appears that if I change the node label string via groovy, that change
is not immediately effective, even if I save the model.
If I launch a subtask from the task that make the label change, that
subtask will run on a node where i
What is the best way to discover all these nice things one could do...? Do
I really need to fire up an IDE and explore the source?
On Sun, Mar 16, 2014 at 1:41 PM, Christian Goetze <
christian.goe...@appdynamics.com> wrote:
> Thank you - that appears to work.
>
>
> On Sun, Ma
Thank you - that appears to work.
On Sun, Mar 16, 2014 at 1:37 PM, Richard Lavoie wrote:
> Have you tried hudson.model.Hudson.instance.save() ?
>
>
> On Sun, Mar 16, 2014 at 4:07 PM, Christian Goetze <
> christian.goe...@appdynamics.com> wrote:
>
>> I recently lea
I recently learned that I can use the script console to run groovy scripts
to modify items in the model.
Specifically, I would like to add, change and remove slave node labels via
a script.
I can make a script like this for example:
hudson.model.Hudson.instance.slaves.each { slave ->
out.pr
Hacky solution:
curl -d 'script=println Jenkins.instance.getItem(jobName).builds.each{
println "${it.number}:${it.startTimeInMillis}:${it.duration}:${it.result}"
};' http://localhost:8080/scriptText
On Thursday, February 20, 2014 5:35:19 PM UTC-8, Christian Goetze wrote:
WHen I run /job//api/json?tree=builds[url], then I get a list
of some builds, but not all the builds I can retrieve via the UI? What's
the magic to get all builds?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group
http://stackoverflow.com/questions/21267270/jenkins-git-plugin-and-reference-repos
I have a bare repo on the same host as the agent, and I get errors like
these:
Error: object directory /.git/objects does not
exist; check .git/objects/info/alternates
the funny thing is that that .git/objects/i
I have a Jenkins job which can get triggered in a variety of ways, either
via SCM polling or via a Gerrit trigger. The order in which the jobs are
run has no real relationship to the ordering of the commits being built, so
comparing the current build with the previous build is not very useful.
11 matches
Mail list logo