need help with commit hooks and build order

[Jim Priest]

I'm getting started with Jenkins and am running into one issue...

I have my GitLab setup with a hook that kicks off my Jenkins job(s)... 

The problem is I several Jenkins jobs

1. Deploy project
2. Run unit tests on project
3. Run integration tests

And my code / tests are in the same project/branch so what happens is these all get kicked off in seemingly random order via the hook.

I had also added a post build action to build the others if each is successful so it ends up running things twice :)

Ideally the hook would kick off my deployment, if that's successful then it would kick of my tests, etc. but I'm not sure of the correct way to wire that up.

Thanks,

Jim

[Marius Gedminas]

On Wed, Mar 04, 2015 at 07:44:05AM -0800, Jim Priest wrote:
> I'm getting started with Jenkins and am running into one issue...
>
> I have my GitLab setup with a hook that kicks off my Jenkins job(s)...
>
> The problem is I several Jenkins jobs
>

> 1. Deploy project
> 2. Run unit tests on project
> 3. Run integration tests

>
> And my code / tests are in the same project/branch so what happens is these
> all get kicked off in seemingly random order via the hook.
>
> I had also added a post build action to build the others if each is
> successful so it ends up running things twice :)
>
> Ideally the hook would kick off my deployment, if that's successful then it
> would kick of my tests, etc. but I'm not sure of the correct way to wire
> that up.

Uncheck "Poll SCM" for jobs 2 and 3, let them get triggered by job 1.

Marius Gedminas
--
As of 2.91, these bugs have all been fixed. We look forward to new ones, well,
not exactly...
-- libstdc++-v3 FAQ