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

Support node-specific Perforce configuration

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Do
    • Component/s: p4-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      (This is sort of related to JENKINS-2947, but doesn't really belong there.)

      The Perforce configuration for a job doesn't provide much flexibility if you want to run a job on various slaves.

      The path to the executable means that the job becomes fixed to an OS (more or less), and doesn't allow for slaves configured with Perforce in a different location.

      The P4PORT setting is also a problem (for me). We have slaves that run in various locations, each of which may have their own local p4 proxy which would be optimal. As it stands now, we have to choose one server that is the best compromise for all locations.

        Attachments

          Issue Links

            Activity

            Hide
            rpetti Rob Petti added a comment -

            This ticket looks like it was made against the perforce-plugin before it was deprecated, and was erroneously moved to p4-plugin. Perforce-plugin is no longer being maintained and has been decommissioned.

            If you are having this issue with the p4-plugin, I recommend opening a new ticket with as much detail as possible so they can resolve the issue.

            Show
            rpetti Rob Petti added a comment - This ticket looks like it was made against the perforce-plugin before it was deprecated, and was erroneously moved to p4-plugin. Perforce-plugin is no longer being maintained and has been decommissioned. If you are having this issue with the p4-plugin, I recommend opening a new ticket with as much detail as possible so they can resolve the issue.
            Hide
            capnjosh Josh Clausen added a comment -

            I have the same use case: multiple locations, each of which has its own p4 proxy (different IPs in every location).

            Right now, the plugin clobbers P4HOST and P4PORT, rather than first checking if there are any existing environment variables by those names.

            So, that would be my recommendation - use any already-set environment variables rather than clobbering those environment variables with whatever happens to be in the form for the credential.

            Show
            capnjosh Josh Clausen added a comment - I have the same use case: multiple locations, each of which has its own p4 proxy (different IPs in every location). Right now, the plugin clobbers P4HOST and P4PORT, rather than first checking if there are any existing environment variables by those names. So, that would be my recommendation - use any already-set environment variables rather than clobbering those environment variables with whatever happens to be in the form for the credential.
            Hide
            rpetti Rob Petti added a comment -

            Sorry, set it to "p4" rather than leave it blank.

            Show
            rpetti Rob Petti added a comment - Sorry, set it to "p4" rather than leave it blank.
            Hide
            ltyphair ltyphair added a comment -

            Leaving the p4 path does not work. Is there a environment variable I can set per node that will work? leaving it blank leaves the command blank even though p4 is in my path.

            Show
            ltyphair ltyphair added a comment - Leaving the p4 path does not work. Is there a environment variable I can set per node that will work? leaving it blank leaves the command blank even though p4 is in my path.
            Hide
            rpetti Rob Petti added a comment -

            Unassigning due to time constraints on my end. If someone else wants to work on this, be my guest.

            Show
            rpetti Rob Petti added a comment - Unassigning due to time constraints on my end. If someone else wants to work on this, be my guest.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oeuftete oeuftete
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: