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

Unable to find latest submitted changelist number when workspace sources are from a Perforce remote depot

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None
    • Jenkins 1.642.2
      P4 Plugin 1.4.14

      The plugin does not currently work with remote depots because it is unable to find the correct changelist to sync against since the metadata for remote depot source is not available. From the log, it looks the like the plugin is doing the following:

      1. First tries to determine the CL via "p4 changes -m1 -ssubmitted //<WorkspaceName>/..."
      2. If it can't, defaults to the latest CL in the server.

      The server CLs aren't associated with the remote depot source CLs, hence the issue.

      I would like to request that the plugin be updated to support remote depots. Perhaps a more complicated CL discovery method can be added in-between the "p4 changes" and latest change methods? Whatever the implementation, the plugin should be smart enough to determine the CL regardless of what type of depot the sources are coming from.

          [JENKINS-42426] Unable to find latest submitted changelist number when workspace sources are from a Perforce remote depot

            Unassigned Unassigned
            carlsej Jason Carlsen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: