-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
Even if the build has failed, the ivy plugin triggers new builds of downstream
projects.
I found no configuration option for triggering other builds (when current is
stable, unstable, failed).
I'm using Ivy plugin 0.3 (with ivy 2.0) and hudson 1.310.
From Console output of a build:
[...]
Email was triggered for: Failure
There are 1 triggered emails.
Sending email for trigger: Failure
Sending e-mails to: ...
No Subversion tagging for unsuccessful build.
Triggering a new build of ActionLib #58
Triggering a new build of Engine3D #44
Triggering a new build of InputLib #23
Finished: FAILURE
====
- depends on
-
JENKINS-5236 DependecyDeclarer always triggers builds and without Actions
-
- Closed
-
- is duplicated by
-
JENKINS-4161 Terminating a build triggers all downstream projects using ivy plugin
-
- Closed
-
[JENKINS-4069] ivy plugin triggers new downstream builds even if current build failed or aborted
Link |
New:
This issue is duplicated by |
Summary | Original: ivy plugin triggers new downstream builds even if current build failed | New: ivy plugin triggers new downstream builds even if current build failed or aborted |
Link |
New:
This issue depends on |
Assignee | Original: hibou [ hibou ] | New: Timothy Bingaman [ tbingaman ] |
added "or aborted" in issue summary to merge
JENKINS-4161with this issue.. they have the same root cause.