Hi, yes you are right, it is not compatible, because you assigned the 'same' job to two different hosts.
The way the plugin works is to wait until all job are finished and then if the only job is the one that should run 'exclusively' then it starts.

Hi Marco, Is there anyway the plugin can be updated to fix the problem? Failing that, do you know of any other plugin/idea I can use to handle my use case?

Thanks, Tom.

Hi, this plugin was developed to run a backup script when no other jobs were running. So it wasn't designed to take into account multiple builds in slaves. I'll need some time to take a look into that to see if the plugin can be modified to suit your needs.
I cannot suggest any workaround because I don't know your needs.

Hi Marco,

Thanks for your reply. I needed a plugin that basically lets me run the same job on the master and all slave nodes when no other jobs are running. In my case, the job I want to run forces Perforce to sync a new development SDK, which can't happen mid build for obvious reasons.

Updating the plugin would be great or if you could suggest an alternative plugin to use that would also be very useful.

Thanks,
Tom.

Hi Marco,

Did you manage to find the time to modify the plugin to support my needs?

Cheers,
Tom.

Hi,

I have a similar request to Tom's. I'm using a matrix project and the Elastic Axes plugin to run a job on all the slaves with a particular label. The job is a housekeeping job and I want to ensure that no other jobs are running while it runs. The Exclusive Execution plugin would be ideal for this if multi-configuration projects were supported. Do you have any plans to add the support?

Ta
Andy