-
Bug
-
Resolution: Fixed
-
Major
-
None
-
linux
my Jenkins job uses p4jenkins (1.1.2) custom view with an assigned workspace name, and runs on a Jenkins slave. When the job starts, p4jenkins create the workspace client and set the root directory to "null" string ( literally 4 chars "null" string)
The prefer way should be a valid root directly at the build node( slave or master). Should be updated according at each build
This causes a problem when using the same workspace client with P4Maven where it expects a valid root directory.
- is related to
-
JENKINS-24512 Add option to lock the created workspace to a host
- Closed
-
JENKINS-26713 P4Jenkins - Modifying Cilentspec Root
- Closed