-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
I tried to use the parameterized trigger and the Join trigger plugin to setup a
build environment of different application which depends on each user.
I tried the following:
- build entire application
- build release 1
- build release 2
- publish results
the publish results job should start if the jobs "build release 1" and "build
release 2" are finished successfully.
If I use both plugins the "publish results" job is triggered directly after the
"build entire application" starts the other jobs.
It works fine if I use the described scenario of the join trigger plugin
including the "build projects after ..." section. But I want to use parameters
of the job "build entire application" in all of the releated projects.
As workaround I will use the default way and copy all parameters to all related
projects.
I tried it with the following versions of the plugin:
Join Plugin - Version: 1.2
Hudson Parameterized Trigger plugin - Version: 1.6 / 2.0
If the plugins are not designed for this usages type, please change the issue
type to enhancement.
[JENKINS-4230] Join Trigger and parameterized-trigger plugin don't work together
gunniman
created issue -
| Component/s | New: join [ 15635 ] | |
| Assignee | Original: huybrechts [ huybrechts ] | New: mdonohue [ mdonohue ] |
| Issue Type | Original: Bug [ 1 ] | New: Improvement [ 4 ] |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: JNJira [ 134303 ] | New: JNJira + In-Review [ 202751 ] |
I'm closing this issue as it was requested from Join 1.2, and this functionality was added in Join 1.6 (however, see
JENKINS-5159for a bug in their interaction that will be fixed in Join 1.7). Please try again when Join 1.7 is released (also with the latest parameterized-trigger plugin), and reopen this or file a new issue if there is still any problem. Thanks!