-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins Docker image 2.263.3, P4-plugin 2.11.1
When upgrading from 1.9.5 to 2.11.1, it seems that matrix builds are broken as far as the Perforce sync is concerned.
Effect of the upgrade: The plugin seems to cache and reuse the last workspace used for a given Perforce changelist. Although two different Perforce clients are defined for the matrix, a wrong client is therefore picked-up leading to the fatal "file not under client's root" message...
Workaround: downgrade to 1.9.5 to get back functional matrix builds
- relates to
-
-
- Open
-
[JENKINS-64879] P4 plugin 2.11.1 broken for matrix builds ?
Philippe Nobili
created issue -
Philippe Nobili
made changes -
| Attachment | New: image-2021-02-19-11-13-52-021.png [ 54026 ] |
Philippe Nobili
added a comment - Hi Karl,
Thanks for the swift reply. Just a bit of context on what we do (the screenshot is below):
We have many branches, but only one to sync. So, depending on what the user selects before building, instead of letting the plugin sync from the depot, we use the CheckOnlyImpl class, and perform the sync ourselves in the build-axis, using the environment variables set-up by the plugin (P4_PORT, P4_CLIENT, etc).
JENKINS_INSTANCE_NAME is defined at Jenkins startup (we build Jenkins as Docker containers on the fly). From what it seems, P4_CLIENT has not the expected value with this version of the plugin, but I might be mistaken... Thanks again.
p4view is correctly defined, using the same environment variables as below and our Perforce depot specifics.
Philippe Nobili
added a comment - Hi Karl,
Thanks for the swift reply. Just a bit of context on what we do (the screenshot is below):
We have many branches, but only one to sync. So, depending on what the user selects before building, instead of letting the plugin sync from the depot, we use the CheckOnlyImpl class, and perform the sync ourselves in the build-axis, using the environment variables set-up by the plugin (P4_PORT, P4_CLIENT , etc).
JENKINS_INSTANCE_NAME is defined at Jenkins startup (we build Jenkins as Docker containers on the fly). From what it seems, P4_CLIENT has not the expected value with this version of the plugin, but I might be mistaken... Thanks again.
p4view is correctly defined, using the same environment variables as below and our Perforce depot specifics.
Karl Wirth
added a comment - Hi pnobili - Thanks. I not familiar with they
I'd like some more detailed information, however it may contain sensitive data so you can either post it here or send an email to support@perforce.com
and mention me in the title. Please get me:
(1) Full console log for a job run that failed on 2.11.1.
(2) Full console log for a job that worked just after the downgrade on 1.9.5.
(3) The build.xml for the job.
Thanks in advance,
Karl
Karl Wirth
added a comment - Hi pnobili - Thanks. I not familiar with they
I'd like some more detailed information, however it may contain sensitive data so you can either post it here or send an email to support@perforce.com and mention me in the title. Please get me:
(1) Full console log for a job run that failed on 2.11.1.
(2) Full console log for a job that worked just after the downgrade on 1.9.5.
(3) The build.xml for the job.
Thanks in advance,
Karl
Karl Wirth
made changes -
| Assignee | New: Karl Wirth [ p4karl ] |
Philippe Nobili
made changes -
| Attachment | New: image-2021-03-04-09-37-39-053.png [ 54114 ] |
Philippe Nobili
made changes -
| Attachment | New: image-2021-03-04-09-38-38-689.png [ 54115 ] |
Philippe Nobili
made changes -
| Attachment | New: image-2021-03-04-09-39-15-452.png [ 54116 ] |
Philippe Nobili
made changes -
| Attachment | New: p4plugin-test.xml [ 54117 ] |
Hi pnobili,
Please get me some screenshots of how the matrix build is defined highlighting the different workspaces so I can try and reproduce this on my test systems.
Regards,
Karl