-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
OS: Windows Server 2008 R2
Jenkins: 1.461, 1.470, 1.473, 1.475
Jenkins Parameterized Trigger plugin: 2.15
SCM Sync Configuration Plugin: 0.0.5
Very simple builds where Build A triggers build B and waits for completion results in the following output:
Started by user anonymous Building in workspace C:\JW\A Waiting for the completion of B
And even after B has completed, A never finishes. Configuration files for builds A and B are attached.
I tested this in all the versions of Jenkins mentioned in the Environment section above and it was present in all of them.
The problem seems to be caused by the SCM Sync Configuration Plugin. I tested it with a fresh install of Jenkins 1.473 and only the two plugins for SCM Sync and Parameterized Trigger enabled and the bug was present. Disabling SCM Sync caused it to go away.
- is related to
-
-
- Closed
-
-
-
- Closed
-
[JENKINS-14329] SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (stuck on waiting for the completion of OtherBuild)
| Component/s | New: core [ 15593 ] | |
| Component/s | New: plugin [ 15491 ] |
| Component/s | New: scm-sync-configuration [ 15757 ] | |
| Component/s | Original: plugin [ 15491 ] | |
| Component/s | Original: core [ 15593 ] | |
| Description |
Original:
Very simple builds where Build {{A}} triggers build {{B}} and waits for completion results in the following output: {noformat} Started by user anonymous [EnvInject] - Loading node environment variables. Building in workspace C:\JW\A Waiting for the completion of B {noformat} And even after {{B}} has completed, {{A}} never finishes. Configuration files for builds {{A}} and {{B}} are attached. We don't have this problem in the last version of Jenkins we were using, {{1.461}}. I don't know if it's something new in {{1.473}}. |
New:
Very simple builds where Build {{A}} triggers build {{B}} and waits for completion results in the following output: {noformat} Started by user anonymous Building in workspace C:\JW\A Waiting for the completion of B {noformat} And even after {{B}} has completed, {{A}} never finishes. Configuration files for builds {{A}} and {{B}} are attached. I tested this in all the versions of Jenkins mentioned in the Environment section above and it was present in all of them. The problem seems to be caused by the SCM Sync Configuration Plugin. I tested it with a fresh install of Jenkins {{1.473}} and only the two plugins for SCM Sync and Parameterized Trigger enabled and the bug was present. Disabling SCM Sync caused it to go away. |
| Environment |
Original:
OS: Windows Server 2008 R2 Jenkins: 1.473 Parameterized Build Trigger plugin: 2.15 |
New:
OS: Windows Server 2008 R2 Jenkins: 1.461, 1.470, 1.473 Jenkins Parameterized Trigger plugin: 2.15 SCM Sync Configuration Plugin: 0.0.5 |
| Summary | Original: Trigger parameterized build and block as build step never returns (waiting for the completion of OtherBuild) | New: SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (suck on waiting for the completion of OtherBuild) |
| Summary | Original: SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (suck on waiting for the completion of OtherBuild) | New: SCM Sync Configuration plugin conflicts with Parameterized Trigger plugin. (stuck on waiting for the completion of OtherBuild) |
I have Jenkins 1.461, Parametrized Trigger Plugin 2.13, and SCM Sync 0.0.4. I Do not experience this issue.
In your A config I see the following line.
<triggerWithNoParameters>false</triggerWithNoParameters>
Looks like you should supply some parameters, but you actually don't. Don't know if that makes a difference.
The test I did was with SCM Sync version 0.0.5, not 0.0.4, I don't know if this was a bug in 0.0.4
As far as the xml element triggerWithNoParameters being false .. I don't know why that's like that. The builds I made are supposed to be the simplest possible case. There is a child build (B) that has no parameters and no build steps, just a blank free-style project. Then there's the parent build (A) that is a free-style project with one build step, to trigger the build of another project and block until it's complete. The xml files I attached are just from doing that. There's no parameters to pass and I don't tell it to pass anything, I don't know why the xml looks the way it does.
With the SCM Sync 0.0.5 enabled the build never finishes (triggers child(B) and B completes, but A just waits there). With the SCM Sync plugin unchecked, build A triggers B as a build step, B completes and then A completes, both builds successful.
Editing description and components to reflect the cause of the problem being the SCM Sync Configuration Plugin.