-
Improvement
-
Resolution: Unresolved
-
Major
-
None
I see there is no way to trigger automatically the downstream build when a project is unstable.
Is it possible to have a default configuration flag inside the main Jenkins configuration or at least in the project configuration?
I need it because we have a Maven multi module project, where each module is compiled separately and we need to work at the same time on projects in different downstream steps.
Jenkins read correctly the upstream and downstream dependencies but when the build is unstable the trigger is not executed, so we can't see if there are any failed tests in the following steps.
I know it is possible to manually set the "trigger even if unstable" specifying the project to build, but this is a very manual and error prone process difficult to maintain.
Is there any solution?
Could you clarify what kind of trigger this issue is about, if not the manual post-build step 'Build other projects'?