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

Cannot change Google Service Account

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I configured and used a google service account in a job.
      Now I want to change that google service account to a new one.
      The two accounts appear in the drop down list in "Google Play Account"
      I can change it to the new one and hit Save. Everything seems to work fine, but when I open the configuration again, it still is on the previous account

        Attachments

          Activity

          Hide
          orrc Christopher Orr added a comment -

          So you mean you can change the service account, and running the job uses the new account, but the wrong one appears in the job config? Do the two accounts have the same name?

          I'll check it out; I need to improve how credentials are configured anyway!

          Show
          orrc Christopher Orr added a comment - So you mean you can change the service account, and running the job uses the new account, but the wrong one appears in the job config? Do the two accounts have the same name? I'll check it out; I need to improve how credentials are configured anyway!
          Hide
          asmodehn Alex V added a comment -

          So after doing more checks, there are two small behaviors that were confusing me:

          • In the job configuration page, the dropdown list of google play accounts always show the first one (even with different names), instead of showing the one actually in the config file (might be the number 2 in the list)
          • The name of the google play account is used in the config file as the ID of that account. As a result you shouldnt have multiple accounts with the same name ( but the credential config page allows you to ), and you cannot rename your account in jenkins settings without reconfiguring your jobs. I dont remember seeing any warning in the credential configuration about it though.

          Cheers !

          Show
          asmodehn Alex V added a comment - So after doing more checks, there are two small behaviors that were confusing me: In the job configuration page, the dropdown list of google play accounts always show the first one (even with different names), instead of showing the one actually in the config file (might be the number 2 in the list) The name of the google play account is used in the config file as the ID of that account. As a result you shouldnt have multiple accounts with the same name ( but the credential config page allows you to ), and you cannot rename your account in jenkins settings without reconfiguring your jobs. I dont remember seeing any warning in the credential configuration about it though. Cheers !
          Hide
          orrc Christopher Orr added a comment -

          Yeah, so I've seen the first issue — that is indeed annoying. It seems to be a bug in the Google OAuth plugin that we depend on; I'd like to remove that dependency for this part of the UI.

          Regarding the unique ID thing, that's also a Google OAuth plugin bug; I filed a bug for that a few weeks ago: JENKINS-29018

          But in the meantime, I added some more checking to the plugin to show better error messages when these kinds of misconfigurations happen.

          Show
          orrc Christopher Orr added a comment - Yeah, so I've seen the first issue — that is indeed annoying. It seems to be a bug in the Google OAuth plugin that we depend on; I'd like to remove that dependency for this part of the UI. Regarding the unique ID thing, that's also a Google OAuth plugin bug; I filed a bug for that a few weeks ago: JENKINS-29018 But in the meantime, I added some more checking to the plugin to show better error messages when these kinds of misconfigurations happen.
          Hide
          orrc Christopher Orr added a comment -

          Version 1.4 of the plugin has now been released, which fixes this issue.

          Show
          orrc Christopher Orr added a comment - Version 1.4 of the plugin has now been released, which fixes this issue.

            People

            • Assignee:
              orrc Christopher Orr
              Reporter:
              asmodehn Alex V
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: