How to specify pre-assignments in Hudson

I have a Hudson assignment that just does a check-out / update in a third party library. Call this job A.

Several other jobs depend on this library. Call them Jobs B and C. They are using Job A verified material and need updating.

My question is, how can I require Jobs B and C to always run Job A (to update the library) before starting their build routine?

If this is not possible, can someone recommend another way to achieve the same effect?

+2


a source to share


3 answers


After thinking about the problem a little more, I think I may have overcomplicated the situation.



Since the library in task A is rarely updated, we decided that it was probably acceptable to just scan the SVN at an interval and update when there are changes. There's a small chance that builds B and C will skip changes to the library if they start right after changes are made to A, but this should rarely be a problem.

0


a source


You can do this in another way with "child" jobs. For example, you can configure A to start B and C after it completes successfully. (You will find the option on the A config configuration page).



If you need more complex conditions for triggering child jobs, you can check out the Parametrized Trigger plugin .

+1


a source


If I follow you, it looks like you might need to Attach the plugin :

This plugin allows you to run a job after all subsequent jobs are completed. This way, execution can fork and execute many steps in parallel, and then run the final aggregation step only once after all the parallel work has finished. The plugin is useful for creating diamond project dependencies. This means that there is one parent job that starts several subsequent jobs. Upon completion of these jobs, one aggregation job is executed

0


a source







All Articles