- The p4 plugin for Jenkins doesn't seem to be able to create a p4 workspace that uses streams, when using Jenkins 2.x's pipeline feature. When doing so, it ends with an error that looks like the following:
ERROR: P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Mapping '//P4Test/Foo/Mainline/...' is not under '//depot/...'.
A full output of a test-build is attached.
Steps to reproduce:
1. start creating a new Jenkins job
2. choose to create a Pipeline job
3. when editing the pipeline's settings, choose to get "Pipeline script from SCM"
4. set the SCM to "Perforce Software"
5. choose appropriate, configured, p4 credentials
6. under "Workspace behavior", choose the option, "Streams (view generated by Perforce for each node)"
7. enter in a stream name. In the attached log, the stream named, "//P4Test/Foo/Mainline" was used. (to note, the stream depot's StreamDepth is set to, "//P4Test/1/2").
8. under "Populate options", choose, "Auto cleanup and sync"
9. enter anything into the "Script Path" box
10. save the job
11. build the job
OBSERVED RESULT: the build fails inside the P4 Plugin, with an error that the stream's path, "is not under '//depot/...'."
EXPECTED RESULT: when building, the P4 Plugin creates and uses workspaces, as appropriate.
NOTES:
- a screenshot of the "Pipeline script from SCM" settings is attached
- the contents of the p4 workspaces that get created are also attached
- the p4 server being used does have a classic, p4 depot attached to it, at //depot/