Hi there, On 08/13/2014 08:27 PM, David Hamm wrote:
i created a google play publisher plugin for android app. the project is located at github:
Ah, I have been working on an extended version of this plugin, as perhaps was somebody else (there was a discussion on the users list recently).
It might be a good idea to integrate with the Google OAuth Plugin, rather than requiring users to have their Google API private key (p12 file) sitting on disk somewhere on the Jenkins master.
This is made more dangerous by the fact that alpha/beta APKs cannot currently be uploaded via the API without also granting the API user permission to alter *production* APKs (amongst other things). I reported this to Google a few days ago, but they "do not currently have a timeline" for it to be fixed.
Otherwise, I'm not sure that defaulting to '**/*.apk' is a great idea, as most release builds produce multiple APKs (unaligned/aligned/unsigned etc.) of which only one should be uploaded, but it seems that given how error handling is implemented, the build will continue in any case and always report success?
Are you sure that removing version codes from other tracks is necessary when uploading; the API seemed to do that automatically (except for the special case of moving from partial rollout to full production)?
Regards, Chris -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
