Hello, We are testing the multiple executor functionality and have run into an odd thing. We set up a node with 4 executors and tied a few jobs to it to run concurrently, repeatedly, to test for file contention and other possible issues.
When we run some of those jobs the system is automatically disabling the job after it completes; whether it fails or succeeds; while other jobs seem unaffected. I have been unable to find any documentation or settings to account for this and it is highly undesirable to disable the jobs. Doing so prevents any further builds until someone manually re-enables them. Has anyone seen this before, or know of a possible cause/solution? If this is expected behavior then that pretty much makes this feature useless. Thanks for any assist, :-) -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Multiple-Executors-Disabling-jobs-tp4764083.html Sent from the Jenkins users mailing list archive at Nabble.com. -- 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/1438963473378-4764083.post%40n4.nabble.com. For more options, visit https://groups.google.com/d/optout.
