[JENKINS-20439] Scoring-load-balancer - Scoring Rule for nodes which have workspace checked out

[jenkins-infra-bot]

Hi,

I have just started using scoring-load-balancer and I really like it!

I want to use it to setup a group of preferred nodes for a job to run. I can also use the 'Scoring by Build Results' to give added preference for the node which was last used for the build.

The problem is I have some monitoring jobs setup to clear out a slaves workspace directory when the slaves free disk space goes below a certain thresehold. This means that the last node the build ran on may no longer have the workspace checked out from svn, but one of the other preferred nodes might have the workspace checked out from an older build.

It would be useful to have a scoring rule that would score based on if the slave has a workspace directory for the job.

This would mean the job would just need to do an svn update and not a full svn checkout.

---

Originally reported by gcummings, imported from: Scoring-load-balancer - Scoring Rule for nodes which have workspace checked out

• status: Open
• priority: Major
• component(s): scoring-load-balancer-plugin
• resolution: Unresolved
• votes: 1
• watchers: 5
• imported: 20251216-225446

Raw content of original issue

Hi,

I have just started using scoring-load-balancer and I really like it!

I want to use it to setup a group of preferred nodes for a job to run.  I can also use the 'Scoring by Build Results' to give added preference for the node which was last used for the build.

The problem is I have some monitoring jobs setup to clear out a slaves workspace directory when the slaves free disk space goes below a certain thresehold.  This means that the last node the build ran on may no longer have the workspace checked out from svn, but one of the other preferred nodes might have the workspace checked out from an older build.

It would be useful to have a scoring rule that would score based on if the slave has a workspace directory for the job.

This would mean the job would just need to do an svn update and not a full svn checkout.

[jenkins-infra-bot]

gcummings:

• Original comment link
• Raw content of original comment:

  I can try and implement this myself if I get time.
  
  I think we might be able to use node.getWorkspaceFor(job) to determine if a node has the workspace.
  

I can try and implement this myself if I get time.

I think we might be able to use node.getWorkspaceFor(job) to determine if a node has the workspace.

[jenkins-infra-bot]

gcummings:

• Original comment link
• Raw content of original comment:

  If a job is configured to "Delete workspace before build starts" from the Workspace Cleanup Plugin then there would be no point in spending time calculating which slaves have the workspace.  Need to find out how to check for this and also work if this plugin is not installed.
  

If a job is configured to "Delete workspace before build starts" from the Workspace Cleanup Plugin then there would be no point in spending time calculating which slaves have the workspace. Need to find out how to check for this and also work if this plugin is not installed.