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

Perforce should factor out global configuration to the global page

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • p4-plugin
    • None
    • Platform: All, OS: All

      The p4 setup puts all configuration options on each project.
      The Jira plugin provides a nice interface for setting up the
      server/username/password in the global config, and then gives a dropdown for
      projects that want Jira integration to select the previously saved server
      settings. This looks like a good model for Perforce.

      The windows specific details seem out of place on the per-project setup screen
      as well, and could move to the global page. They could also use some
      reasonable default values, to help users get this right.

          [JENKINS-2947] Perforce should factor out global configuration to the global page

          mdonohue created issue -

          Kohsuke Kawaguchi added a comment -

          Un-assigning this from digerata per request by him.

          Kohsuke Kawaguchi added a comment - Un-assigning this from digerata per request by him.

          Rob Petti added a comment -

          Windows specific details, and the path to the perforce executable are not needed in the p4java version we're developing, so I think those will stay where they are for now.

          I do like that model of selecting from a predefined list of p4 servers that are defined globally, though. I'll look into it if i can find the time

          Rob Petti added a comment - Windows specific details, and the path to the perforce executable are not needed in the p4java version we're developing, so I think those will stay where they are for now. I do like that model of selecting from a predefined list of p4 servers that are defined globally, though. I'll look into it if i can find the time
          Rob Petti made changes -
          Assignee New: Rob Petti [ rpetti ]

          Carl Quinn added a comment -

          It seems that there would be two distinct setting groups that could be managed globally:

          • node tool specifics: p4 path, Windows specific details
          • depot specifics: P4PORT, username, password, repository browser

          Then each project would select the desired logical depot, and the node's tools settings would define the node-local values for p4.

          Carl Quinn added a comment - It seems that there would be two distinct setting groups that could be managed globally: node tool specifics: p4 path, Windows specific details depot specifics: P4PORT, username, password, repository browser Then each project would select the desired logical depot, and the node's tools settings would define the node-local values for p4.

          Rob Petti added a comment -

          JENKINS-5120 Wants node-level overrides for logical depot settings as well...

          Rob Petti added a comment - JENKINS-5120 Wants node-level overrides for logical depot settings as well...
          Rob Petti made changes -
          Assignee Original: Rob Petti [ rpetti ]
          Rob Petti made changes -
          Link New: This issue is blocking JENKINS-5120 [ JENKINS-5120 ]
          Rob Petti made changes -
          Link New: This issue is related to JENKINS-7192 [ JENKINS-7192 ]
          Rob Petti made changes -
          Link Original: This issue is related to JENKINS-7192 [ JENKINS-7192 ]

            Unassigned Unassigned
            mdonohue mdonohue
            Votes:
            6 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: