I'm currently working on further acceptance tests for the NodeLabelParameter plugin within the scope of U. Hafners student projects. At the moment I'm struggling to define a valid use case to test the triggerIfResult options (run next build only if build succeeds, etc.) of the plugin.
I tried to set up a freestyle job parameterized with a node parameter (no default node, no node restriction, next build triggered only if build succeeds and node eligibility set to all nodes). To simulate failed or unstable builds I use the text-finder plugin as post build action. The particular slave the job shall be build on contains a text file in its workspace which causes the plugin to mark the build as failed or unstable. I built the job on multiple (dumb) slaves which were prepared to get a failed result. My expectation was that as the first build is failed the other builds won't start. But I always get builds on all slaves. It would be helpful to know in which case those triggerIfResult options are evaluated and whether I need to add further settings, parameters and / or post build actions to the job. Or may be the text-finder plugin is not the appropriate way to simulate failed builds. I'm open to alternative suggestions. -- Martin -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
