-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Windows XP Pro sp3
Hudson (version 1.347)
Join plugin (version 1.8)
Hudson Parameterized Trigger plugin (version 2.3)
Have the "Join plugin" (version 1.8 ) and "Hudson Parameterized Trigger plugin" (version 2.3) installed.
On my Project configuration, I have the "Run post-build actions at join" checked so that I can have my other projects parameterized triggered. Unfortunately, that project never gets executed.
The normal join project however gets triggered (only the parameterized does not).
Thanks
- depends on
-
-
- Closed
-
- is blocking
-
JENKINS-6071 Send parameterized-trigger variables/values to the join job as well
-
- Resolved
-
- is duplicated by
-
-
- Closed
-
[JENKINS-5602] Run parameterized-trigger after join does not work
akusuma
created issue -
illenseer
made changes -
| Environment | Original: Windows XP Pro sp3 |
New:
Windows XP Pro sp3 Hudson (version 1.347) Join plugin (version 1.8) Hudson Parameterized Trigger plugin (version 2.3) |
mdonohue
added a comment - Do you get any stack traces in the console output when the parameterized build is supposed to start, but doesn't?
mdonohue
added a comment - Do you get any stack traces in the console output when the parameterized build is supposed to start, but doesn't? 
natashadev
added a comment - I see the same problem with XP Pro SP2, Hudson 1.349, Join 1.8 and Hudson Parameterized Trigger 2.3. No stack track in the logs (loglevel FINEST).
natashadev
added a comment - I see the same problem with XP Pro SP2, Hudson 1.349, Join 1.8 and Hudson Parameterized Trigger 2.3. No stack track in the logs (loglevel FINEST). 
sauravsengupta
added a comment - I'm seeing this behavior too. XP Pro SP3,same Hudson and plugin versions, no stack traces. If I check the 'aggregate downstream archives' option, that one does fire (I think I got a log saying 'nothing to aggregate'). I took a brief look through the code, and it looked like both plugins were triggered using the same mechanism, which makes me wonder if the issue is in the Parameterized Trigger plugin, rather than the Join plugin.
I'd like to say that this used to work when I started using Hudson (which was about a month or so ago) and stopped working after some upgrade, but I can't say for sure.
I posted a repro here before I knew that I wasn't supposed to post in that forum.
sauravsengupta
added a comment - I'm seeing this behavior too. XP Pro SP3,same Hudson and plugin versions, no stack traces. If I check the 'aggregate downstream archives' option, that one does fire (I think I got a log saying 'nothing to aggregate'). I took a brief look through the code, and it looked like both plugins were triggered using the same mechanism, which makes me wonder if the issue is in the Parameterized Trigger plugin, rather than the Join plugin.
I'd like to say that this used to work when I started using Hudson (which was about a month or so ago) and stopped working after some upgrade, but I can't say for sure.
I posted a repro here before I knew that I wasn't supposed to post in that forum. illenseer
added a comment - I also do not get any stack traces. mdonohue
added a comment - JENKINS-5981, filed against the parameterized trigger plugin seems to suffer from a similar underlying issue.
mdonohue
added a comment - JENKINS-5981 , filed against the parameterized trigger plugin seems to suffer from a similar underlying issue. mdonohue
made changes -
| Link |
New:
This issue depends on |
mdonohue
made changes -
| Component/s | New: parameterized-trigger [ 15592 ] | |
| Summary | Original: "Run post-build actions at join" does not work | New: Run parameterized-trigger after join does not work |
I am experiencing the exactly same issue here with my Hudson installation (same plugin versions).