Branch: refs/heads/feature/JENKINS-62404_custom-release-tracks
Home: https://github.com/jenkinsci/google-play-android-publisher-plugin
Commit: 5433eedc47b92195fb1691334622df7da204b745
https://github.com/jenkinsci/google-play-android-publisher-plugin/commit/5433eedc47b92195fb1691334622df7da204b745
Author: Christopher Orr <[email protected]>
Date: 2020-05-23 (Sat, 23 May 2020)
Changed paths:
M
src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/ApkUploadTask.java
M
src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/TrackAssignmentTask.java
M
src/test/java/org/jenkinsci/plugins/googleplayandroidpublisher/ApkPublisherTest.java
M
src/test/java/org/jenkinsci/plugins/googleplayandroidpublisher/ReleaseTrackAssignmentBuilderTest.java
Log Message:
-----------
Deal with the Google Play API not always responding with all tracks.
If you ask the API for a list of tracks, you'll only get back those
which already have at least one release defined. 🤷♀️
This is inconvenient, as track names are case-sensitive, therefore we
try to read the list of available tracks, so we can ensure that we use
the canonical track name when calling the API, regardless of what the
user provided in the job configuration.
So now we show a warning if the track could not be found, but continue
with the operation anyway, assuming that the track actually does exist,
and the user entered the track name correctly.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-commits/jenkinsci/google-play-android-publisher-plugin/push/refs/heads/feature/JENKINS-62404_custom-release-tracks/13f601-5433ee%40github.com.
