Does that problem always occur? (every time you launch a build of that parent project?)

  • I have about 10 consecutive builds (last 10) of the parent project that displayed this issue and needed to be aborted, so yes.

Do parent builds run on slaves?

  • Parent builds run on the master, triggers another separate project to create slaves for the child project discussed here, and then builds the child project.

Does that problem occur on any slaves? Or only on a specific slave?

  • The build trigger duplication issue happens on the master, since it is the executor that triggers the child project. The slaves that are created earlier in the parent project are only connected to the child project through a node label (so that they will accept child project builds).

Do builds stop to proceed after parameterized-trigger starts? (that is, parameterized-trigger doesn't finish?)

  • It appears as if the build trigger step does finish (as you will see in the log), since the console continues to the next build step. I suspect this doesn't matter, necessarily, since the trigger for the Child project has the "Block until triggered projects finish" setting unchecked.

Config.xml and Console output? Sure. I'll go get them.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to