HI, I am trying to launch a multijob via postman and for some reason whatever the result of the job phases contained in it another build of the multijob is automatically triggered. The contained jobs just then sit there waiting to execute on the same node the multijob is now running on until I disable and abort it.
If I run this multijob via the Jenkins front end it works as expected and I can't see why it would behave differently when triggered remotely? Anyone seen this before? Thanks Steve -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9a004c24-98fd-401b-96e7-3aba051cd879%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
