Hi Ralph,
This is a bug. The generated jobs should never be called by the generators.
Feel free to enter an issue in Jira with the xml files of your projects so
I will be able to reproduce your use case.
Thank you,
syl20bnr
Le vendredi 2 mai 2014 12:44:29 UTC-4, Ralph Bolton a écrit :
>
&g
HI Balázs,
Parameters file are not supported yet in a post-build action but it should
be doable, can you fill a JIRA ticket here [1] ?
Can you fill a second one for the bug with parameters file when
Parameterized Build Trigger is used as a build step ?
Thank you,
syl20bnr
[1]
https
prevent spaghetti build history of jobs).
Cheers,
syl20bnr
Le mercredi 10 juillet 2013 15:41:20 UTC-4, Daniel Beck a écrit :
>
> How would this solve the complexity problem of manually triggering
> downstream jobs? Quoting Maureen:
>
> > In my case the processes are fired off
You can also use the build parameterized trigger plugin you already use to
read from the property file using "Parameters from properties file". The
plus sides are that build parameters are recorded in build histories and
the values will be set before that the SCM step occurs.
Cheers
. I'm the author of the last one. :-)
Cheers,
syl20bnr
--
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...@googlegroup
ly 2 jobs it may be not worth it.
Cheers,
syl20bnr
Le vendredi 5 juillet 2013 15:30:48 UTC-4, Srinivasan Ponnuswamy a écrit :
>
> I need to have two jenkins build jobs for a same project in same brach but
> with different goals.
>
> It is just like having a copy of job with differe
I create a ticket you can follow. I'll investigate if this is possible to
completely remove the quiet period.
https://issues.jenkins-ci.org/browse/JENKINS-17843
Cheers,
syl20bnr
Le jeudi 2 mai 2013 10:10:02 UTC-4, Walter Kacynski a écrit :
>
> I'm using the Job Generator plugin
If you use downsream/upstream jobs, you can take a look
at https://wiki.jenkins-ci.org/display/JENKINS/Job+Generator+Plugin
Cheers,
syl20bnr
Le vendredi 29 mars 2013 16:13:27 UTC-4, harperville a écrit :
>
> I'm in the same boat. The definition of a pipeline is based on
> upstr
ng https://wiki.jenkins-ci.org/display/JENKINS/Job+Generator+Plugin
which I developed for this specific case.
Cheers,
syl20bnr
Le vendredi 29 mars 2013 16:13:27 UTC-4, harperville a écrit :
>
> I'm in the same boat. The definition of a pipeline is based on
> upstream/downstream dep
What you are looking for
is https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
The downside is that it does not use the build in downstream and upstream
relationship between jobs and some plugin may not work properly.
The upside is that it is the best plugin to orchestrate build flows.
If those plugins answer your question you can check for the Job Generator
plugin to generate cleaned job configurations without the conditional steps.
Cheers,
syl20bnr
Le vendredi 15 mars 2013 14:39:40 UTC-4, cchen a écrit :
>
> Hello,
>
> Is there a way to bind a build parameter
A job generator requires the master to be able to execute jobs, a job generator
cannot be executed on a slave.
Can you check the number of available executors for your Jenkins server in the
settings page ?
Cheers,
syl20bnr
--
You received this message because you are subscribed to the Google
Hello,
If you have some kind of pipeline approach then you could have a look at
the Job Generator plugin which is aimed to define job templates. We are
using it at work to generate 100+ jobs defined by 20 Job Generators. Maybe
it could help you.
Cheers,
syl20bnr
Le jeudi 31 janvier 2013 08
AFAIK, it's not possible to do this out of the box.
You may be able to do this by extending the Free Style Job in the code and
providing a new Next button or by coding new parameters with dynamic content
(not sure about this one) but it requires to code a new plugin.
Cheers,
syl20bnr
example on the wiki page:
https://wiki.jenkins-ci.org/display/JENKINS/Job+Generator+Plugin
Cheers,
syl20bnr
Le vendredi 18 janvier 2013 11:34:56 UTC-5, Mandeville, Rob a écrit :
>
> I need to rebuild databases on my build servers on a regular basis. In
> order to do this, I have a re
t; using the delete mode.
>
> syl20bnr wrote:
> > Thank you for the details. I can reproduce it.
> > There is some sort of deadlock if your master is configured with more
> > than 1 executor.
> > The deletion should be done one by one or I have to find a way anothe
Once I restart Jenkins, the invincible jobs are gone of course and some
> of the projects they were intended to delete have gone away. As I said,
> I only see this problem when using the delete mode. Creating brand new
> or replacing existing jobs works fine. It looks like there's some
> Once I restart Jenkins, the invincible jobs are gone of course and some
> of the projects they were intended to delete have gone away. As I said,
> I only see this problem when using the delete mode. Creating brand new
> or replacing existing jobs works fine. It looks like there'
Can you give me more details on your hierarchy so I can try to reproduce
this bug ?
Thank you.
Le jeudi 3 janvier 2013 23:02:15 UTC-5, JonathanRRogers a écrit :
>
> Whenever I run a job generator job to delete an existing hierarchy of
> generated jobs, the generator jobs themselves get stuck. Th
19 matches
Mail list logo
