p4 plugin crashes when used from parallel scripted pipeline

XMLWordPrintable

    • Type: Bug
    • Resolution: Postponed
    • Priority: Major
    • Component/s: p4-plugin
    • None

      I am using version 1.6.1 of the P4 plugin and evaluating the change introduced for JENKINS-43281.

      My script invokes checkout as follows:

                  checkout([$class: 'PerforceScm', credential: 'jenkinsbuild', populate: [$class: 'SyncOnlyImpl', have: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', path: '/usr/local/bin/p4', threads: '4'], pin: '', quiet: true, revert: false], workspace: [$class: 'StaticWorkspaceImpl', charset: 'none', name: p4clientName, pinHost: true]])

       

      I see the behavior shown in the attachment. There are two issues here. The first is that we are still creating the clone, so it doesn't look like the JIRA issue was really fixed. The second is that we are hitting a null pointer exception.

      We should not be using this JIRA to track the update behavior of static-sync workspaces. That is more properly in 43281.

       

        1. P4Clone.txt
          4 kB
          Steven Gardell
        2. example.groovy
          7 kB
          Steven Gardell

            Assignee:
            Paul Allen
            Reporter:
            Steven Gardell
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: