|
||||||||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
I would like to reopen this issue. I have a different reason for wanting a possibility to tie projects or jobs to specific executors:
I have a configuration with parametrized projects with persistent work spaces local to the slave the jobs happen to execute on. The work spaces are based on the ${EXECUTOR} variable to separate them, and are reused by a lot of projects. It can take up to 10 minutes to initialize a workspace (cleaning etc.), and I would like to clean these work spaces from time to time, to reduce initialization time for production jobs. The idea I have to go about this is to trigger cleaning jobs on specific executors, so that each persistent workspace will be cleaned without locking all the executors. I haven't been able to find any way to tie a specific executor for jobs.
Neither neither port allocator nor locks & latches or throttle concurrent builds appear to allow this.