Add "dont trigger downstream jobs" as part of Jenkins core

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

Add "dont trigger downstream jobs" as part of Jenkins core

jaakkoo
Hi,

I've been wondering is it possible to create a job that has an
downstream but it does not automatically trigger the downstream when
job finishes. It seems, that it's not possible. I have an situation
where the "motherjob" would actually trigger around 3600 jobs (300
matrix jobs), and I really try to avoid situation like that. But i
still need to have it as downstream because I need to block all other
jobs if the "motherjob" is building.

So I would like to get your opinion could it be possible to get an
option "don't trigger downstream jobs after finished" as part of the
core? I can create and send you the patch, but i prefer not to create
any fork of my Jenkins if my idea is not accepted by the ones deciding
if it's worth to implement as part of the "main core".

BR,
Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

Alan Harder-2
Could you use parameterized trigger plugin to make them downstream, but
using some trigger condition that never happens? (if there is such a
trigger..)


On 04/04/11 12:21, jaakkoo wrote:

> Hi,
>
> I've been wondering is it possible to create a job that has an
> downstream but it does not automatically trigger the downstream when
> job finishes. It seems, that it's not possible. I have an situation
> where the "motherjob" would actually trigger around 3600 jobs (300
> matrix jobs), and I really try to avoid situation like that. But i
> still need to have it as downstream because I need to block all other
> jobs if the "motherjob" is building.
>
> So I would like to get your opinion could it be possible to get an
> option "don't trigger downstream jobs after finished" as part of the
> core? I can create and send you the patch, but i prefer not to create
> any fork of my Jenkins if my idea is not accepted by the ones deciding
> if it's worth to implement as part of the "main core".
>
> BR,
> Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

ben732@gmail.com
In reply to this post by jaakkoo
I recently had a similar need and the "don't trigger downstream build" option would really help. It would maintain the relationship between the two but still allow independent triggers.

I say +1...

-----Original Message-----
Date: Monday, April 04, 2011 5:02:16 pm
To: [hidden email]
From: "Alan Harder" <[hidden email]>
Subject: Re: Add "dont trigger downstream jobs" as part of Jenkins core

Could you use parameterized trigger plugin to make them downstream, but
using some trigger condition that never happens? (if there is such a
trigger..)


On 04/04/11 12:21, jaakkoo wrote:

> Hi,
>
> I've been wondering is it possible to create a job that has an
> downstream but it does not automatically trigger the downstream when
> job finishes. It seems, that it's not possible. I have an situation
> where the "motherjob" would actually trigger around 3600 jobs (300
> matrix jobs), and I really try to avoid situation like that. But i
> still need to have it as downstream because I need to block all other
> jobs if the "motherjob" is building.
>
> So I would like to get your opinion could it be possible to get an
> option "don't trigger downstream jobs after finished" as part of the
> core? I can create and send you the patch, but i prefer not to create
> any fork of my Jenkins if my idea is not accepted by the ones deciding
> if it's worth to implement as part of the "main core".
>
> BR,
> Jaakko


Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

Geoff Bullen
We had the same problem when we were creating the build-pipeline
plugin so we set up a manual downstream job option.  This maintains
the relationship between jobs, but the downstream isn't automatically
triggered (we add a button to the view for this).

We will be releasing a new version this week, which is worth waiting
for as it fixes some quite critical issues.

Cheers, Geoff

On Apr 5, 8:21 am, "[hidden email]" <[hidden email]> wrote:

> I recently had a similar need and the "don't trigger downstream build" option would really help. It would maintain the relationship between the two but still allow independent triggers.
>
> I say +1...
>
>
>
>
>
>
>
> -----Original Message-----
> Date: Monday, April 04, 2011 5:02:16 pm
> To: [hidden email]
> From: "Alan Harder" <[hidden email]>
> Subject: Re: Add "dont trigger downstream jobs" as part of Jenkins core
>
> Could you use parameterized trigger plugin to make them downstream, but
> using some trigger condition that never happens? (if there is such a
> trigger..)
>
> On 04/04/11 12:21, jaakkoo wrote:
> > Hi,
>
> > I've been wondering is it possible to create a job that has an
> > downstream but it does not automatically trigger the downstream when
> > job finishes. It seems, that it's not possible. I have an situation
> > where the "motherjob" would actually trigger around 3600 jobs (300
> > matrix jobs), and I really try to avoid situation like that. But i
> > still need to have it as downstream because I need to block all other
> > jobs if the "motherjob" is building.
>
> > So I would like to get your opinion could it be possible to get an
> > option "don't trigger downstream jobs after finished" as part of the
> > core? I can create and send you the patch, but i prefer not to create
> > any fork of my Jenkins if my idea is not accepted by the ones deciding
> > if it's worth to implement as part of the "main core".
>
> > BR,
> > Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

jaakkoo
Nice :)

Is your plugin able to handle more than one downstream jobs? I've
tested your plugin a few times, and i remember that you were only able
to specify one downstream job? Also it would be nice that i could use
regex to specify downstream :)

Cheers,
Jaakko


On Apr 5, 1:49 am, Geoff Bullen <[hidden email]> wrote:

> We had the same problem when we were creating the build-pipeline
> plugin so we set up a manual downstream job option.  This maintains
> the relationship between jobs, but the downstream isn't automatically
> triggered (we add a button to the view for this).
>
> We will be releasing a new version this week, which is worth waiting
> for as it fixes some quite critical issues.
>
> Cheers, Geoff
>
> On Apr 5, 8:21 am, "[hidden email]" <[hidden email]> wrote:
>
>
>
>
>
>
>
> > I recently had a similar need and the "don't trigger downstream build" option would really help. It would maintain the relationship between the two but still allow independent triggers.
>
> > I say +1...
>
> > -----Original Message-----
> > Date: Monday, April 04, 2011 5:02:16 pm
> > To: [hidden email]
> > From: "Alan Harder" <[hidden email]>
> > Subject: Re: Add "dont trigger downstream jobs" as part of Jenkins core
>
> > Could you use parameterized trigger plugin to make them downstream, but
> > using some trigger condition that never happens? (if there is such a
> > trigger..)
>
> > On 04/04/11 12:21, jaakkoo wrote:
> > > Hi,
>
> > > I've been wondering is it possible to create a job that has an
> > > downstream but it does not automatically trigger the downstream when
> > > job finishes. It seems, that it's not possible. I have an situation
> > > where the "motherjob" would actually trigger around 3600 jobs (300
> > > matrix jobs), and I really try to avoid situation like that. But i
> > > still need to have it as downstream because I need to block all other
> > > jobs if the "motherjob" is building.
>
> > > So I would like to get your opinion could it be possible to get an
> > > option "don't trigger downstream jobs after finished" as part of the
> > > core? I can create and send you the patch, but i prefer not to create
> > > any fork of my Jenkins if my idea is not accepted by the ones deciding
> > > if it's worth to implement as part of the "main core".
>
> > > BR,
> > > Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

Geoff Bullen
Our next release (coming this week) will handle multiple downstream
jobs.  It won't support the join plugin get though.   Have a look at
the ticket http://code.google.com/p/build-pipeline-plugin/issues/detail?id=3
for details of how it might look.

I'll post to the Jenkins users group when it's been released.

Cheers,

Geoff


On Apr 5, 3:35 pm, jaakkoo <[hidden email]> wrote:

> Nice :)
>
> Is your plugin able to handle more than one downstream jobs? I've
> tested your plugin a few times, and i remember that you were only able
> to specify one downstream job? Also it would be nice that i could use
> regex to specify downstream :)
>
> Cheers,
> Jaakko
>
> On Apr 5, 1:49 am, Geoff Bullen <[hidden email]> wrote:
>
>
>
>
>
>
>
> > We had the same problem when we were creating the build-pipeline
> > plugin so we set up a manual downstream job option.  This maintains
> > the relationship between jobs, but the downstream isn't automatically
> > triggered (we add a button to the view for this).
>
> > We will be releasing a new version this week, which is worth waiting
> > for as it fixes some quite critical issues.
>
> > Cheers, Geoff
>
> > On Apr 5, 8:21 am, "[hidden email]" <[hidden email]> wrote:
>
> > > I recently had a similar need and the "don't trigger downstream build" option would really help. It would maintain the relationship between the two but still allow independent triggers.
>
> > > I say +1...
>
> > > -----Original Message-----
> > > Date: Monday, April 04, 2011 5:02:16 pm
> > > To: [hidden email]
> > > From: "Alan Harder" <[hidden email]>
> > > Subject: Re: Add "dont trigger downstream jobs" as part of Jenkins core
>
> > > Could you use parameterized trigger plugin to make them downstream, but
> > > using some trigger condition that never happens? (if there is such a
> > > trigger..)
>
> > > On 04/04/11 12:21, jaakkoo wrote:
> > > > Hi,
>
> > > > I've been wondering is it possible to create a job that has an
> > > > downstream but it does not automatically trigger the downstream when
> > > > job finishes. It seems, that it's not possible. I have an situation
> > > > where the "motherjob" would actually trigger around 3600 jobs (300
> > > > matrix jobs), and I really try to avoid situation like that. But i
> > > > still need to have it as downstream because I need to block all other
> > > > jobs if the "motherjob" is building.
>
> > > > So I would like to get your opinion could it be possible to get an
> > > > option "don't trigger downstream jobs after finished" as part of the
> > > > core? I can create and send you the patch, but i prefer not to create
> > > > any fork of my Jenkins if my idea is not accepted by the ones deciding
> > > > if it's worth to implement as part of the "main core".
>
> > > > BR,
> > > > Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

jaakkoo
Looks nice.. I'll take it in to use as soon as you release it :) It
will be a test how your plugin scales since we have around 3600
jobs :)

Cheers,
Jaakko

On Apr 5, 10:13 am, Geoff Bullen <[hidden email]> wrote:

> Our next release (coming this week) will handle multiple downstream
> jobs.  It won't support the join plugin get though.   Have a look at
> the tickethttp://code.google.com/p/build-pipeline-plugin/issues/detail?id=3
> for details of how it might look.
>
> I'll post to the Jenkins users group when it's been released.
>
> Cheers,
>
> Geoff
>
> On Apr 5, 3:35 pm, jaakkoo <[hidden email]> wrote:
>
>
>
>
>
>
>
> > Nice :)
>
> > Is your plugin able to handle more than one downstream jobs? I've
> > tested your plugin a few times, and i remember that you were only able
> > to specify one downstream job? Also it would be nice that i could use
> > regex to specify downstream :)
>
> > Cheers,
> > Jaakko
>
> > On Apr 5, 1:49 am, Geoff Bullen <[hidden email]> wrote:
>
> > > We had the same problem when we were creating the build-pipeline
> > > plugin so we set up a manual downstream job option.  This maintains
> > > the relationship between jobs, but the downstream isn't automatically
> > > triggered (we add a button to the view for this).
>
> > > We will be releasing a new version this week, which is worth waiting
> > > for as it fixes some quite critical issues.
>
> > > Cheers, Geoff
>
> > > On Apr 5, 8:21 am, "[hidden email]" <[hidden email]> wrote:
>
> > > > I recently had a similar need and the "don't trigger downstream build" option would really help. It would maintain the relationship between the two but still allow independent triggers.
>
> > > > I say +1...
>
> > > > -----Original Message-----
> > > > Date: Monday, April 04, 2011 5:02:16 pm
> > > > To: [hidden email]
> > > > From: "Alan Harder" <[hidden email]>
> > > > Subject: Re: Add "dont trigger downstream jobs" as part of Jenkins core
>
> > > > Could you use parameterized trigger plugin to make them downstream, but
> > > > using some trigger condition that never happens? (if there is such a
> > > > trigger..)
>
> > > > On 04/04/11 12:21, jaakkoo wrote:
> > > > > Hi,
>
> > > > > I've been wondering is it possible to create a job that has an
> > > > > downstream but it does not automatically trigger the downstream when
> > > > > job finishes. It seems, that it's not possible. I have an situation
> > > > > where the "motherjob" would actually trigger around 3600 jobs (300
> > > > > matrix jobs), and I really try to avoid situation like that. But i
> > > > > still need to have it as downstream because I need to block all other
> > > > > jobs if the "motherjob" is building.
>
> > > > > So I would like to get your opinion could it be possible to get an
> > > > > option "don't trigger downstream jobs after finished" as part of the
> > > > > core? I can create and send you the patch, but i prefer not to create
> > > > > any fork of my Jenkins if my idea is not accepted by the ones deciding
> > > > > if it's worth to implement as part of the "main core".
>
> > > > > BR,
> > > > > Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

Geoff Bullen
In reply to this post by jaakkoo
Wow that is a lot.  Would you be willing to test the pre-release
version for us?  If so, send me an email -
[hidden email]

Out of interest...  do you have any good strategies for managing so
many jobs?    Such as bulk configuration changes and keeping so many
jobs\views manageable...

Cheers,

Geoff

On Apr 5, 5:21 am, jaakkoo <[hidden email]> wrote:

> Hi,
>
> I've been wondering is it possible to create a job that has an
> downstream but it does not automatically trigger the downstream when
> job finishes. It seems, that it's not possible. I have an situation
> where the "motherjob" would actually trigger around 3600 jobs (300
> matrix jobs), and I really try to avoid situation like that. But i
> still need to have it as downstream because I need to block all other
> jobs if the "motherjob" is building.
>
> So I would like to get your opinion could it be possible to get an
> option "don't trigger downstream jobs after finished" as part of the
> core? I can create and send you the patch, but i prefer not to create
> any fork of my Jenkins if my idea is not accepted by the ones deciding
> if it's worth to implement as part of the "main core".
>
> BR,
> Jaakko
Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

Andrew Gray
Hi Jaakko,

Just out of interest (I'm sure someone else out there is wondering the same thing)

...what sort of system has 3600 build jobs?

Cheers,

Andrew

On 6 April 2011 12:31, Geoff Bullen <[hidden email]> wrote:
Wow that is a lot.  Would you be willing to test the pre-release
version for us?  If so, send me an email -
[hidden email]

Out of interest...  do you have any good strategies for managing so
many jobs?    Such as bulk configuration changes and keeping so many
jobs\views manageable...

Cheers,

Geoff

On Apr 5, 5:21 am, jaakkoo <[hidden email]> wrote:
> Hi,
>
> I've been wondering is it possible to create a job that has an
> downstream but it does not automatically trigger the downstream when
> job finishes. It seems, that it's not possible. I have an situation
> where the "motherjob" would actually trigger around 3600 jobs (300
> matrix jobs), and I really try to avoid situation like that. But i
> still need to have it as downstream because I need to block all other
> jobs if the "motherjob" is building.
>
> So I would like to get your opinion could it be possible to get an
> option "don't trigger downstream jobs after finished" as part of the
> core? I can create and send you the patch, but i prefer not to create
> any fork of my Jenkins if my idea is not accepted by the ones deciding
> if it's worth to implement as part of the "main core".
>
> BR,
> Jaakko

Reply | Threaded
Open this post in threaded view
|

Re: Add "dont trigger downstream jobs" as part of Jenkins core

jaakkoo
Hi,

What we are actual developing, consists of Kernel/OS, platform and
applications. And I usually take the platform side as an example, it
consists of about 300 components, and they are compiled to 12
different architectures (mips, ppc etc.). So if you add up 12*300 you
end with 3600 jobs. Of course this is not all, but they are actually
part of one Jenkins instance at the moment.

Geoff:
Our jenkins instance is pretty open in a way, developers can freely
add and remove components from the CI -system. The idea is that,
there's one "template" available and you just modify everything to
it:
Specify what architectures your component support
Specify to what product it belongs
Specify the component name

In our case Jenkins is only used for "frontend" - to make things
visible in a nice way. The backend is much more complicated: It takes
care that if you specify "I want to work on component A".. And in
order that you can actually work with component A you need to have the
whole upstream available, so the backend fetches the upstream compiles
the component A, fetches downstream and compiles the downstream
against it. And so on :)

Cheers,
Jaakko


On Apr 6, 7:17 am, Andrew Gray <[hidden email]> wrote:

> Hi Jaakko,
>
> Just out of interest (I'm sure someone else out there is wondering the same
> thing)
>
> ...what sort of system has 3600 build jobs?
>
> Cheers,
>
> Andrew
>
> On 6 April 2011 12:31, Geoff Bullen <[hidden email]> wrote:
>
>
>
>
>
>
>
> > Wow that is a lot.  Would you be willing to test the pre-release
> > version for us?  If so, send me an email -
> > [hidden email]
>
> > Out of interest...  do you have any good strategies for managing so
> > many jobs?    Such as bulk configuration changes and keeping so many
> > jobs\views manageable...
>
> > Cheers,
>
> > Geoff
>
> > On Apr 5, 5:21 am, jaakkoo <[hidden email]> wrote:
> > > Hi,
>
> > > I've been wondering is it possible to create a job that has an
> > > downstream but it does not automatically trigger the downstream when
> > > job finishes. It seems, that it's not possible. I have an situation
> > > where the "motherjob" would actually trigger around 3600 jobs (300
> > > matrix jobs), and I really try to avoid situation like that. But i
> > > still need to have it as downstream because I need to block all other
> > > jobs if the "motherjob" is building.
>
> > > So I would like to get your opinion could it be possible to get an
> > > option "don't trigger downstream jobs after finished" as part of the
> > > core? I can create and send you the patch, but i prefer not to create
> > > any fork of my Jenkins if my idea is not accepted by the ones deciding
> > > if it's worth to implement as part of the "main core".
>
> > > BR,
> > > Jaakko