Behalf Of Daniel Beck
Sent: Monday, August 26, 2013 4:48 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: "Build after other projects are built" question
Right, my examples would remove the build trigger completely until added again
in the config of downstream projects.
Have you tri
t the downstream
> job never get triggered? Why would it work sometimes but not others?
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
> Sent: Monday, August 26, 2013 3:34 PM
> To: jenkin
metimes but not others?
-Original Message-
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck
Sent: Monday, August 26, 2013 3:34 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: "Build after other projects are built" que
'Build after other projects are built' is actually stored in the _triggering_
job as a post-build action. Check the config.xml's of the triggering and
triggered jobs. It's just a UI trick that you're able to configure this from
the downstream job.
Any of the following will cause a job's templat
Hi,
We are using the "Build after other projects are built" feature...
Job B is triggered to run after Job A runs. Job A is based on a CloudBees
Template. The build trigger is set on Job B, not Job A.
Sometimes it works correctly (i.e. Job A runs and Job B is triggered. When it
works correctly
