FYI, I thought a saw problems 'copying' jobs. In your example, if jobc
or jobd when created were copied from jobb, it causes problems for me.
Internally join thinks their all jobB or something.
So, if you created any of these jobs by copying another job, I would
start over.
I don't use join much anymore because I need the 'main job', jobA to
stick over until everybody is done so my details about the issue might
be a little foggy.
Doug
On Oct 18, 5:32 am, David Kennedy <
[hidden email]> wrote:
> For what it's worth, I'm having an issue where I've four sets of four builds
> like you describe, but only two of them join properly. I can't see a
> different between the working builds' configurations and the non-working
> configuration.
>
> You might be doing something slightly wrong, or you might be the victim of
> my hard-to-figure-out bug. (Or my bug might be misconfig I can't spot).
>
> My workaround that usually works:
> (1) Delete all build triggers etc from all builds in the join, A included
> (2) Set up A again
>
>
>
>
>
>
>
> On Mon, Oct 17, 2011 at 4:49 PM, Lars Nordin <
[hidden email]> wrote:
> > I’m having trouble getting the join plugin working and I am wondering how
> > to configure jobs so that join works. I think I have the configuration
> > correctly but the joining job is not triggered.****
>
> > I’m running Jenkins 1.406 and Join plugin v1.13****
>
> > ** **
>
> > I have a layout of job A triggers jobs B, C and D and then jobs B, C and D
> > trigger job E.****
>
> > From the wiki page for the join plugin, I see that I need to configure:***
> > *
>
> > ** **
>
> > JobA:****
>
> > Build other projects: jobB, jobC, jobD****
>
> > Join Trigger: jobE****
>
> > ** **
>
> > ** **
>
> > JobB JobC and JobD:****
>
> > Build after other projects are built: jobA****
>
> > Build other projects: not checked****
>
> > Join Trigger: not checked****
>
> > ** **
>
> > JobE:****
>
> > Build after other projects are built: not checked (Is this correct?) **
> > **
>
> > Join Trigger: not checked****
Locked
