Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50674

Switch from Perforce plugin (discontinued) to P4 plugin

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Critical Critical
    • jira-plugin

      The Perforce plugin seems discontinued or at least no longer maintained (https://wiki.jenkins.io/display/JENKINS/Perforce+Plugin). The P4 plugin seems to be the recommended new choice.

      At this moment I get this warning in jenkins.

      Perforce Plugin 1.3.36
Job-specific credentials can be obtained by users with Job/Extended Read permission
Ineffective credentials encryption

      Since the jira-plugin is needed because of blue-ocean, it's not like some plugins can be disabled.

          [JENKINS-50674] Switch from Perforce plugin (discontinued) to P4 plugin

          Oleg Nenashev added a comment -

          JIRA plugin has been recently excluded from BlueOcean FYI (see conversation log in JENKINS-48357)
          CC michaelneale coervivek

          Oleg Nenashev added a comment - JIRA plugin has been recently excluded from BlueOcean FYI (see conversation log in JENKINS-48357 ) CC michaelneale coervivek

          Michael Neale added a comment -

          oleg_nenashev not quite - I think that has to be rolled back temporarily, so it will be part of it, however there is a plan to fix up the JIRA plugin. I am not sure of the connection with perforce? 

           

          FYI if ther eis an issue the JIRA plugni can be disabled, the blueocean-JIRA plugin will complain but it wont' affect any non JIRA functionality, but just be an ugly (temporary) error. 

          Michael Neale added a comment - oleg_nenashev not quite - I think that has to be rolled back temporarily, so it will be part of it, however there is a plan to fix up the JIRA plugin. I am not sure of the connection with perforce?    FYI if ther eis an issue the JIRA plugni can be disabled, the blueocean-JIRA plugin will complain but it wont' affect any non JIRA functionality, but just be an ugly (temporary) error. 

          Oleg Nenashev added a comment -

          Yes, there should be no functional impact for missing optional deps excepting logging. CC danielbeck just to confirm

          Oleg Nenashev added a comment - Yes, there should be no functional impact for missing optional deps excepting logging. CC danielbeck just to confirm

          Daniel Beck added a comment -

          perforce is an optional dependency of jira plugin, so I would expect that it (perforce) can be removed without negative impact (but it's not possible through the UI due to a bug in the plugin manager).

          Looking over the code it's possible the optional dependency is not properly implemented (i.e. to fail loading if the plugin isn't available), but I haven't tested it.

          Daniel Beck added a comment - perforce is an optional dependency of  jira plugin, so I would expect that it (perforce) can be removed without negative impact (but it's not possible through the UI due to a bug in the plugin manager). Looking over the code it's possible the optional dependency is not properly implemented (i.e. to fail loading if the plugin isn't available), but I haven't tested it.

          Heiko Nardmann added a comment -

          To me it looks like this one can be closed?

          Heiko Nardmann added a comment - To me it looks like this one can be closed?

            cwarden Christian Warden
            daften Dieter Blomme
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: