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

integrate hudson perforce with multiple p4 locations

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: perforce-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      The hudson perforce plugin is limited to synchronization with one
      directory/depot path. That is, when configuring a project, we will have to
      specify on the depot path line just the following:

      //depot/directory/...

      If there are multiple projects that we may or many not need to synchronize with,
      we will end up synching with much more than necessary.

      The situation we have is, we do have multiple projects, as follows:

      //depot/directory/project1/...
      //depot/directory/build_scripts_project1/...
      //depot/directory/project2/...
      //depot/directory/build_scripts_project2/...
      //depot/directory/project3/...
      //depot/directory/build_scripts_project3/...
      //depot/directory/common_resources/...
      //depot/directory/build_scripts_common_resources/...

      Now, all projects require the common resources (and it's corresponding build
      directory). So, far the only way to synch with each project is to use the depot
      path: //depot/directory/...

      This causes too much inefficiency in terms of space and time. Can you add a
      feature to allow us to specify individual projects/p4 modules as is the case in
      a normal p4 client spec?

      Thanks!

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              aklintu aklintu
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: