In the absence of any further action recently from myself or David, I'm
going to try and fix up the proposed changes to the dependent
google-oauth-plugin, and release my plugin by the end of next week.
Regards,
Chris
On 08/29/2014 10:03 AM, Sandell, Robert wrote:
Though I guess it would be nice if somebody would help decide which of these
proposed plugins should be actually submitted to the jenkinsci repo :)
In my experience when this happens it is usually solved by one of the plugin
authors recognising that the other's is the better one and both partys decide
on a way forward to incorporate missing features from one plugin to the other.
In this case if I read between the lines correctly is that both of you are
kindly asking the other to cave in, but it doesn't seem to happen ;) So this is
where my experience ends.
You both seem to recognize though that there can be only one.
Coin toss, Quake Deathmatch, or maybe bring it to the Governance Board to
review both and decide on which one to go with?
Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Christopher Orr
Sent: den 29 augusti 2014 01:59
To: Jenkins Dev
Subject: Re: New Plugin: google play publisher
On 08/20/2014 01:45 PM, Jerome Lacoste wrote:
On Tuesday, August 19, 2014 4:51:24 PM UTC+2, Christopher wrote:
Hey,
So as I mentioned earlier (and I kinda mentioned on the users mailing
list a few weeks ago), I had starting working on basically the same
plugin.
I finally got some time to finish the first version and do lots of
testing with it (apparently the Google Play API has a "daily save
quota", which makes testing fun...).
The code is now on GitHub:
https://github.com/orrc/google-play-android-publisher-plugin
<https://github.com/orrc/google-play-android-publisher-plugin>
To be honest, I'm not sure what should be done in this situation, where
two people have developed similar plugins at the same time.
While your plugin probably works fine, I think that my version has a
few
improvements:
- Works on Jenkins slaves (not just the master)
- Supports uploading and assigning multiple APKs
- Supports staged rollouts
- Allows uploading of "What's new" text for multiple languages
- Changes the build result to failed if the configuration is bad, or
uploading APKs fails for some reason
- Every configuration field supports variable expansion, making the
plugin more flexible
- Integrates with the Google OAuth Plugin, so that credentials can be
entered once globally, rather than having to configure credentials for
every job
Here's a screenshot for anybody interested:
https://lh3.googleusercontent.com/-vk6N5JlEBlE/U_KH3iettFI/AAAAAAAABKI/ru7pNaKiv-4/w711-h597-no/google-play-android-publisher.png
<https://lh3.googleusercontent.com/-vk6N5JlEBlE/U_KH3iettFI/AAAAAAAABK
I/ru7pNaKiv-4/w711-h597-no/google-play-android-publisher.png>
I've been playing with the API for uploading screenshots, so my
intention was to add another Recorder which can upload screenshots and
listing texts for all the various languages.
Does anybody have any input here? :)
This is pretty cool and I will try the plugin as soon as I can.
Cool, I've had some people compiling and trying it out and I haven't heard any
complaints so far.. ;)
Though I guess it would be nice if somebody would help decide which of these
proposed plugins should be actually submitted to the jenkinsci repo :)
As for uploading screenshots/texts, I am not sure. My current process
(which involves deploying to various stores - apple-amazon-play-etc),
takes as input a directory layout with text files and images, structured
per store / language / resolutions etc.
If I had to bake this into a plugin, I would probably appreciate
something like
* take this directory/zip as source
* take this this format as input. E.g.
%locale%/%type%/Screenshot%idx%.png
or
PlayStore/Screenshot%idx%_%locale%_/%type%_.png
or whatever the user wants to use to create his layout.
Yeah, that's an interesting idea. I have a matrix job which generates
screenshots in a similar pattern, with different folders for each
language. So this would be nicer than having to manually configure each
language in advance in the job config.
Thanks for the feedback!
Note: I haven't looked at the Play API at all yet.
It's a bit weird, especially the Java SDK. The documentation isn't
great either. Plus the API account setup process isn't 100%
straightforward in Google Play.
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.
