Jenkins: a heavily branched chain of build jobs

[Виталий Исаев]

We would like to set up Continuous Integration and Continuous Deployment processes on the base of Jenkins ecosystem. Currently we're trying to put together all the Jenkins build jobs we have (from sources to several endpoint processes launched on the testing server). There are three kinds of build/deployment processes in our case:

1. Building deb packages from C++ projects (some of them are dependent, others are dependencies);
2. Building images from Docker containers;
3. Launching some processes in the endpoint;

As you can notice, we faced with a heavily branched chain of jobs triggered by each other. And every update of any of the upstream projects must go throughout the chain of jobs and trigger the final job (process I). So It would be nice to use some kind of Jenkins plugins that will:

• Control such a complicated structure of jobs (I tried to use Build Pipeline Plugin and I got the impression that this tool is suitable for "linear" job chains);
• Provide clean way of passing the parameters between job environments.

Any help will be appreciated.

(repost from SO).

[Baptiste Mathus]

I think you should have a look at the workflow plugin (beware, not build flow which is somehow deprecated).

Cheers

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c45a42b2-4b0f-4943-ba42-071262e0dac0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.