Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: google-play-android-publisher-plugin
-
Environment:Linux Debian Wheezy
-
Similar Issues:
Description
After creating a Google Play credentials as explained in the Wiki for this plugin, and configuring the job where I see the credential pop-up listing my only user.
But when the job executes, I get this error:
15:05:12 Upload failed: org.jenkinsci.plugins.googleplayandroidpublisher.UploadException: Credentials for the configured Google Account could not be found
15:05:12 at org.jenkinsci.plugins.googleplayandroidpublisher.GooglePlayPublisher.getServiceAccountCredentials(GooglePlayPublisher.java:39)
15:05:12 at org.jenkinsci.plugins.googleplayandroidpublisher.ApkPublisher.perform(ApkPublisher.java:301)
15:05:12 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
15:05:12 at hudson.model.Build$BuildExecution.post2(Build.java:182)
15:05:12 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
15:05:12 at hudson.model.Run.execute(Run.java:1731)
15:05:12 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
15:05:12 at hudson.model.ResourceController.execute(ResourceController.java:88)
15:05:12 at hudson.model.Executor.run(Executor.java:232)
Looking at the config.xml for this job shows that there is no "googleCredentialsId" field (which explains the stacktrace above).
After I added a second credential, the build worked correctly, and the config.xml was correct.
Steps to reproduce:
- Start with no google play account credentials stored
- Create one, upload the p12 file
- Setup a new job, the credential pop-up lists the only user
- Run the build
The scenario as described shouldn't be possible, and I can only reproduce this if I create a job before any credentials have been created.
Adding more credentials to Jenkins won't cause the "googleCredentialsId" to be set in any job, unless the job configuration page is opened, and then the Save button is clicked.
But it's a known issue that the error messages relating to credentials can be improved, and the plugin should also be able to handle renaming of credentials, as currently renaming credentials after a job has been configured causes the above stacktrace.