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

Could we use masked password variable in Perforce Depot->Password

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I use mask password plugin and I set it in Global Properties ->Mask Passwords - Global name/password pairs

      In a job > Source Code Management>Perforce > Depot>Password, could I use a mask variable set globally?

      Thanks!

      KC

        Attachments

          Activity

          Hide
          llamahunter Richard Lee added a comment -

          Ah.. I must have overlooked that. Is there a bug on that I can follow? Or should I file a new one?

          Show
          llamahunter Richard Lee added a comment - Ah.. I must have overlooked that. Is there a bug on that I can follow? Or should I file a new one?
          Hide
          rpetti Rob Petti added a comment -

          JENKINS-14787 covers this. I've got a branch with experimental changes that might resolve the issue, but I haven't had the chance to test it yet.

          Show
          rpetti Rob Petti added a comment - JENKINS-14787 covers this. I've got a branch with experimental changes that might resolve the issue, but I haven't had the chance to test it yet.
          Hide
          shobhad Shobha Dashottar added a comment -

          Has anyone got this working. I tried but the Perforce Plugin didn't accept the parameter substitution
          I am using
          Masked Password - 2.7.2
          Perforce - 1.3.27
          Jenkins 1.498

          Show
          shobhad Shobha Dashottar added a comment - Has anyone got this working. I tried but the Perforce Plugin didn't accept the parameter substitution I am using Masked Password - 2.7.2 Perforce - 1.3.27 Jenkins 1.498
          Hide
          rpetti Rob Petti added a comment -

          It works fine for me. Don't forget to enable the mask passwords plugin in your job's environment, and use the proper format for parameter references when typing it into the password field, ie: ${PASSWORDVARIABLE}

          Also, do not use P4PASSWD as the parameter name... that might screw it up.

          Show
          rpetti Rob Petti added a comment - It works fine for me. Don't forget to enable the mask passwords plugin in your job's environment, and use the proper format for parameter references when typing it into the password field, ie: ${PASSWORDVARIABLE} Also, do not use P4PASSWD as the parameter name... that might screw it up.
          Hide
          shobhad Shobha Dashottar added a comment -

          Thanks Rob. It helped. Looks like it is working fine now as I ran the groovy script and it is giving me the right password. Previously, I was using P4PASSWD and that was the only change I made today. Unfortunately, we still have a problem with the AD account as it gets locked even after running the build job just once. If I use a non-AD perforce user, this is working just fine.

          Show
          shobhad Shobha Dashottar added a comment - Thanks Rob. It helped. Looks like it is working fine now as I ran the groovy script and it is giving me the right password. Previously, I was using P4PASSWD and that was the only change I made today. Unfortunately, we still have a problem with the AD account as it gets locked even after running the build job just once. If I use a non-AD perforce user, this is working just fine.

            People

            • Assignee:
              Unassigned
              Reporter:
              kevinchow Kevin Chow
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: