-
Bug
-
Resolution: Duplicate
-
Major
-
Jenkins 2.7.3
Pipeline 2.4
Multibranch 2.9
There seems to be a recent change in strategy on how folders are organized in workspace folder on Jenkins master for first stage SCM checkouts from multibranch jobs. Previously they used to be nested folders now they are not.
My problem is, there seems to be a size limit on the workspace subfolder name and you are cropping the git repository name, which is causing some maintenance problems. e.g.
A pull request to a Git repository name 'navigation extension' is cropped to some thing like this:
avigation-extension_PR-2464-KJBGB3QGPGBXAOYPEHJ33MLLSHZ5D7E5YXNLYLFVQGYPXWOKA4CQ@script
Another one 'aws-infrastructure-data' is something like:
-infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script
so naturally you cannot do something like:
$ cd -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script -bash: cd: -i: invalid option cd: usage: cd [-L|[-P [-e]] [-@]] [dir]
Secondly, the path seems to be too long which can also create some problems.
- is duplicated by
-
-
- Resolved
-
[JENKINS-38506] Invalid workspace path for pipeline jobs on jenkins master
Nick Archibald
made changes -
| Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
| Description |
Original:
There seems to be a recent change in strategy on how folders are organized in workspace folder on Jenkins master for first stage SCM checkouts from multibranch jobs. Previously they used to be nested folders now they are not. My problem is there is seems to be size limit on the workspace subfolder name and you are cropping the git repository name, which is causing some maintenance problems. e.g. A pull request to a Git repository name '_navigation extension_' is cropped to some thing like this: {code:none} avigation-extension_PR-2464-KJBGB3QGPGBXAOYPEHJ33MLLSHZ5D7E5YXNLYLFVQGYPXWOKA4CQ@script {code} Another one '_aws-infrastructure-data_' is something like: {code:none} -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script {code} so naturally you cannot do something like: {code:none} $ cd -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script -bash: cd: -i: invalid option cd: usage: cd [-L|[-P [-e]] [-@]] [dir] {code} |
New:
There seems to be a recent change in strategy on how folders are organized in workspace folder on Jenkins master for first stage SCM checkouts from multibranch jobs. Previously they used to be nested folders now they are not. My problem is, there seems to be a size limit on the workspace subfolder name and you are cropping the git repository name, which is causing some maintenance problems. e.g. A pull request to a Git repository name '_navigation extension_' is cropped to some thing like this: {code:none} avigation-extension_PR-2464-KJBGB3QGPGBXAOYPEHJ33MLLSHZ5D7E5YXNLYLFVQGYPXWOKA4CQ@script {code} Another one '_aws-infrastructure-data_' is something like: {code:none} -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script {code} so naturally you cannot do something like: {code:none} $ cd -infrastructure-data_master-O7PVEBG7YU24BDNRZTSG3VBPTCGPVWE5PF2OZ35TBWNASAJB2OOA@script -bash: cd: -i: invalid option cd: usage: cd [-L|[-P [-e]] [-@]] [dir] {code} Secondly, the path seems to be too long which can also create some problems. |
| Link |
New:
This issue is duplicated by |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |