[JIRA] (JENKINS-47442) Parameterized Trigger hangs waiting for downstream job

0 views
Skip to first unread message

nl.travis@yahoo.com (JIRA)

unread,
Nov 19, 2018, 1:17:02 PM11/19/18
to jenkinsc...@googlegroups.com
Travis Neal commented on Bug JENKINS-47442
 
Re: Parameterized Trigger hangs waiting for downstream job

Was this ever fixed for you guys? we're running into the same issues. We tried downgrading to 2.32 but this is lower than required for the Git plugin (which requires 2.33, which is the breaking version) downgrading the Git plugin to allow the parameterized trigger plugin to work correctly would mean removing core functionality from our Jenkins implementation.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.hermon@fisglobal.com (JIRA)

unread,
Nov 19, 2018, 4:11:02 PM11/19/18
to jenkinsc...@googlegroups.com

We were never able to get it working, we've since switched to kicking off the build from our normal jobs instead of from the Promoted Builds plugin.

reiner.wirtz@ser.de (JIRA)

unread,
Nov 20, 2018, 6:08:02 AM11/20/18
to jenkinsc...@googlegroups.com

 We transformed most of our jenkins jobs to jenkins pipeline.

We never got a problem starting another jenkins job from piepeline.

 

olivier.schiavo@mybestpro.com (JIRA)

unread,
Feb 4, 2020, 6:44:03 AM2/4/20
to jenkinsc...@googlegroups.com

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.

 

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages