Geek asks and answers

Define selective blocking of up / down jobs in Jenkins

I have set up several jobs with automatic start between them.

All tasks have both “Block assembly when an upstream project is under construction” and “Block assembly when a project is downstream” is built on “true”. It worked fine until there was a need for additional work to load artifacts from other jobs.

This is a lengthy process that I do not want to block the entire conveyor of the building. So I separated it as a job. It is launched by all other jobs and pushes artifacts to a remote server with a low bandwidth connection.

But they are still waiting because of the settings mentioned.

Is there a way to make them not wait for this particular job? Maybe the approach is wrong, and this should not be a task for them? If not - how to control the execution of other tasks and easily collect the results? Maybe there is some non-blocking alternative for ArtifactDeployer that just sets the task and ends - I don’t need to collect the results of the download task?

+5
source share
2 answers

I myself found the answer. It was right in front of my eyes ...

I missed a very important part of the Parametrized Trigger plugin: if you use it as a build step and do not perform post-build, it can either wait or not wait for the result of subsequent work. The flow down looks like a "(non-blocking)" subproject of a job up.

+6
source

Jenkins Build Flow, DSL - , .

+1

More articles:


All Articles