Issue Type: Improvement Improvement
Assignee: Unassigned
Components: heavy-job-plugin
Created: 23/Apr/15 9:46 AM
Description:

heavy-job-plugin randomly picks an executor on the slave node to actually run the job and marks the other "n-1" executors as unavailable.
We use a maven repository-per-executor and this behaviour means that all the repositories eventually get very large.
If the executor picked was consistently the lowest-numbered one (ie. #1 on a slave where all are allocated to the heavy job) this would help.
Perhaps this could be configured via a checkbox "Use first available executor on the slave".

Environment: heavy-job-plugin 1.1
jenkins 1.596.2
Project: Jenkins
Labels: heavy-job
Priority: Minor Minor
Reporter: Ed Randall
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.

Reply via email to