| If someone is still reading this, here is the workaround I found: I made an ugly patch, just return always false in the canDeclare() method
diff --git a/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java b/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
index 746d209..5232a99 100644
--- a/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
+++ b/src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
@@ -196,7 +196,8 @@ public class TriggerBuilder extends Builder implements DependencyDeclarer {
private boolean canDeclare(AbstractProject owner) {
// See HUDSON-5679 -- dependency graph is also not used when triggered from a promotion
- return !owner.getClass().getName().equals("hudson.plugins.promoted_builds.PromotionProcess");
+ //return !owner.getClass().getName().equals("hudson.plugins.promoted_builds.PromotionProcess");
+ return false;
}
@Override
The problem arised with dependency management, which is clearly broken. The "patch" just bypasses the dependency management in all cases, no just the promotion. Even with the patch, when you look the build cause of the triggered job it is broken. |