|
We fight an ongoing battle here with long file name problems under windows. We bought ourselves like two years by letting Jenkins/Perforce lay down the workspace, but then doing the build under a "subst" drive.
Recently though, it has come to past that it is Perforce Plugin that gets the error . . . the names of the source are very long coming right out of the depot.
I'd really like to stay away from custom workspaces, but that is the ultimate control. However, it seems to me that the Jenkins core could reasonably do a number of things to help:
Slaves:
We pretty much control the Slave root (thank you), but "workspace" is a long word. (Yes our pain level is such that we look at even those 9 characters and sigh.) It would be nice if we could control that . . . or perhaps allow us to optionally use "ws" instead.
Master and Slaves:
Users understandably use expressive jobs names . . . it would be nice if a short replacement for these could be found . . . perhaps something like the build history where there are two names connected by a symlink. As our user push the 20 to 40 character Job Names, their directory paths become overly long. It would be nice to have a short name generated some how that was used for most everything . . . save the symlink versions for Humans trying to find their build by hand. (Or not, mostly this is an debug concern and most folks doing this know to pull the path out of the buils console.)
I won't even talk about matrix projects . . . the parm1/value/parm2/value is crazy painful . . . fortunately our build folks haven't tried to use it (yet) . . .
Yeah, I know, use Linux . . . and we are moving in that direction. It would just be nice if the Jenkins Gods could consider long path problems for any changes they make.
Consider this: the default IMS installer leaves the workspace at C:\Program Files (x86)\Jenkins\workspace (40 chars) plus up to another 40 for job name . . . so out of the box Jenkins currently uses 15% to 30% of the "path space" . . . seems like that could be reduced just by being more careful and thinking about your window brothers as you code. <wink>
Sorry . . . I just had to get it off my chest.
|
