Making Jenkins (Hudson) job depend on another job

Question

I have two jobs:

1. Upload
2. Launch-instance

I want to make Launch-instance dependent on the other one, so that triggering Launch-instance automatically causes Upload to be run first.

Can I achieve this using built-in Jenkins features or with a plugin?

Note that I do not want Upload to always trigger Launch-instance, which is what the "Build after other projects are built" option on Launch-instance would do. What I want is more analogous to how depends attribute works in Ant.

Answer 1

Have you tried the Parametrized Trigger Plugin?

You can use it as a build step, and mark the checkbox for "Block until the triggered projects finish their builds". That should be exactly what you are looking for.

Answer 2

Aha, found it! Here I'm building on miki's answer which showed the way but didn't fully solve this for me.

As it says in the Spanish-language article about launching Hudson builds which was linked to from the comments of Hudson's Remote access API page that miki linked to:

En la sección "Build Triggers" [...] marcamos la opción "Trigger builds remotely (e.g., from scripts)". Al marcar esta opción vemos como aparece el cuadro de texto "Authentication Token". Aquí pondremos el nombre del token de autenticación.

_{(source: adictosaltrabajo.com)}

(It seems the benefits of knowing Spanish are starting to materialise... :-)

So, turns out Hudson provides a handy built-in option for triggering builds remotely. In Build Triggers section (of Upload job in my case) you can enable remote builds and set an auth token (see screenshot above). Then you can launch a build by accessing a certain URL containing that token. In my case, the first build step of Launch-instance looks like:

wget http://[hudson-url]/job/Upload/build?token=TEST
sleep 10

This works even if anonymous builds are disabled and simply trying to access the build URL would yield "403 Forbidden".

Answer 3

Running dependent job via wget is not a general solution. Since jobs are run asynchornnously your Launch-job will not be hang and wait for Upload job for a completion. using sleep is just a dirty hack and is not an option for most cases... IMHO the best solution is to use: http://wiki.jenkins-ci.org/display/JENKINS/Join+Plugin

Answer 4

What about building Upload by calling its build URL with wget as the first build step? Then adding the beef build steps of Launch-instance.

Or for a fancier approach, perhaps use the Remote access API.

Answer 5

You can use the downstream or upstream dependencies. You should use "Build Triggers" -> Build after other projects are built and/or post-build actions in the configure part of the project.