jenkinsci / jenkinsci/workflow-aggregator-plugin

[JENKINS-56692] Invalid directory name after pipeline workspace truncation

Open
#976 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

component:pipeline imported-jira-issue priority:major resolution:unresolved
Dominant language
No language data
Stars
225
Forks
125
PR merge metrics
No merged PRs in 30d

Description

Jenkins creates directories with invalid names.

This results in git checkouts HANGING on the slave machine.

 

It intentionally truncates directory names for workspaces, to avoid problems on systems like Windows.

That truncation can lead to directories beginning with invalid characters like -.

This makes it impossible to delete those directories from the command line.

Removal requires using Screen Sharing.app to launch Finder.app to remove the workspace directories from SSH slaves.

 

Please add a single [a-zA-Z] character at the beginning of any truncated name which doesn't start with a character in that set.

See also JENKINS-46493, JENKINS-54869, JENKINS-54640.

---
Originally reported by timshadel, imported from: Invalid directory name after pipeline workspace truncation


  • status: Open
  • priority: Major
  • component(s): pipeline
  • resolution: Unresolved
  • votes: 0
  • watchers: 1
  • imported: 2025-12-08

Raw content of original issue

Jenkins creates directories with invalid names.

This results in git checkouts HANGING on the slave machine.

 

It intentionally truncates directory names for workspaces, to avoid problems on systems like Windows.

That truncation can lead to directories beginning with invalid characters like -.

This makes it impossible to delete those directories from the command line.

Removal requires using Screen Sharing.app to launch Finder.app to remove the workspace directories from SSH slaves.

 

Please add a single [a-zA-Z] character at the beginning of any truncated name which doesn't start with a character in that set.

See also JENKINS-46493, JENKINS-54869, JENKINS-54640.

environment

```
macOS 10.14.3

Jenkins LTS 2.150.3

Pipeline 2.6
```

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file, test, or entry point is named. Start by locating the pipeline workspace-name truncation logic and reproduce the leading-character case described; done means truncated names that do not begin with an ASCII letter are prefixed with one and the affected checkout scenario no longer hangs.

Written by the indexing model from the issue text.

Assessment

Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.