-
New Feature
-
Resolution: Unresolved
-
Trivial
-
Version 1.7.6
With latest p4-plugin, repository browser option is not being saved and always revert back to Auto.
On our environment, p4-plug always fail to detect with auto option.
P4 Task: saving built changes.
Found last change 25335 on syncID jenkins-******-CI
... p4 client -o jenkins-*****-CI
+
... p4 info
+
... p4 client -o jenkins-*****-CI
+
... p4 info
+
... done
[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
java.lang.NullPointerException
at org.jenkinsci.plugins.p4.client.ConnectionHelper.getSwarm(ConnectionHelper.java:595)
at org.jenkinsci.plugins.p4.changes.P4ChangeParser$ChangeLogHandler.<init>(P4ChangeParser.java:73)
at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:48)
Caused: org.xml.sax.SAXException: Could not parse perforce changelog:
java.lang.NullPointerException
at org.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:53)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:812)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.access$1500(WorkflowRun.java:135)
at org.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:1002)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:127)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:130)
at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:59)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:263)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:419)
Finished: FAILURE
[JENKINS-47394] Hide 'Repository browser' field for legacy Perforce 'Global Pipeline libraries' - Repository browser not saved
Comment |
[ Hi, This issue is marked as Trivial but I think it's more than just the settings panel displaying incorrectly. As far as I can tell the repository browser option doesn't work at all (for multi-branch pipeline projects). Since we exclusively use multi-branch pipelines that means we can't use the delta links from the build pages, which would be really handy otherwise (linking to swarm). I tried a non-pipeline job and the Swarm links worked correctly. Kind Regards, Mat Bailey Unit 2 Games ] |
Labels | New: P4_VERIFY |
Labels | Original: P4_VERIFY | New: P4_BACKLOG |
Summary | Original: Repository browser not saved | New: Hide 'Repository browser' field for legacy Perforce 'Global Pipeline libraries' - Repository browser not saved |
Attachment | New: image-2020-06-25-09-01-19-562.png [ 51747 ] |
Attachment | New: image-2020-06-25-09-01-49-883.png [ 51748 ] |