triple-t/gradle-play-publisher

GPP is Android's unofficial release automation Gradle Plugin. It can do anything from building, uploading, and then promoting your App Bundle or APK to...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 16th, 2026
Created on August 7th, 2014
Open Issues & Pull Requests: 22 (+0)
GitHub issues: Enabled
Number of forks: 349
Total Stargazers: 4,318 (+0)
Total Subscribers: 78 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.5 hours
Mean response time: 35.2 days
90th percentile: 21.3 days
Tracked items: 36

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,215 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (21)
  • waiting-for-reply (20)
  • dontclose (10)
  • enhancement (10)
  • docs (6)
  • feature:other (4)
  • blocked-by-api (1)
  • feature:listing (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Gradle Play Publisher is a Gradle plugin that automates the release workflow for Android applications to the Google Play Store.

The tool addresses the friction of manual Play Store uploads and metadata management by integrating directly into the Gradle build system. It handles the complete release pipeline: building App Bundles or APKs, uploading them to Play Console, promoting releases through internal testing and staged rollout phases, and publishing app listings along with screenshots, descriptions, and other store metadata. By treating these operations as Gradle tasks, it enables developers to script and automate their entire release process as part of their build pipeline.

Teams should adopt this tool if they want to eliminate manual Play Store interactions and integrate release automation into their CI/CD workflows. It suits projects of any size that publish regularly to the Play Store and benefit from reproducible, scriptable deployments. The plugin is particularly valuable for teams practicing continuous delivery who want to reduce human error and accelerate time-to-market for updates.

The project shows consistent maintenance with regular commits addressing bug fixes and feature additions. Pull requests receive timely review and feedback from maintainers. The codebase demonstrates active development with ongoing refinements to support evolving Play Console APIs and Gradle versions. Issue discussions indicate responsive engagement with user-reported problems and feature requests.