aspect to control when downstream jobs should be build

[rhaschke]

I noticed that jenkins doesn't build downstream jobs anymore if the build is unstable. Maybe the following options are new to jenkins:

However, to ensure that my downstream jobs are build, even when an upstream one is unstable only, I need to set those options from the build-generator, based on the variable orchestration.success-results. Is there already a way to accomplish this?

[scymtym]

This is not yet supported. I'm adding a new variable dependencies.required-upstream-result to control this behavior.

[scymtym]

I'm currently thinking about having a pair of variables

• dependencies.required-upstream-result one of success, unstable, any
• dependencies.required-result one of success, unstable, any

with following associated behavior:

• The value of dependencies.required-upstream-result in a downstream job controls the result threshold that upstream jobs of the job in question have to satisfy in order for the downstream job to get triggered.
• The value of dependencies.required-result in an upstream allows relaxing the above constraints for all downstream jobs of the upstream job.

For example, if job a triggers job b and

• job b has dependencies.required-upstream-result = success
• job a has dependencies.required-result = unstable

the effective threshold in job b will be unstable.

The intention is to mark certain projects as "flaky" (i.e. test failures should not prevent downstream builds) using the dependencies.required-result variable without the need to adjust each downstream project.

[rhaschke]

Sounds reasonable.