acdt (Android Continuous Deployment Tools) is a toolset to interact with the Google Play Store API and the Gitlab API.
Google Play Store:
- list all apk already published
- publish a new version of an app
Gitlab:
- create a new release
- update a release
- delete a release
Changelog:
- Generate a changelog from release note files
./acdt -h
Usage: commandline [OPTIONS] COMMAND [ARGS]...
Options:
--version Show the version and exit
-h, --help Show this message and exit
Commands:
play-store-publish Publish app on the play store
play-store-list-apks List all apk published on the play store
gitlab-create-release Create gitlab release
gitlab-update-release Update gitlab release
gitlab-delete-release Delete gitlab release
gitlab-close-milestone Close gitlab milestone
changelog-generate Generate changelog
./acdt play-store-list-apks -h
Usage: commandline play-store-list-apks [OPTIONS]
List all apk published on the play store
Options:
-c, --credentials-p12 PATH Credentials p12 file
-i, --service-account-id TEXT Service account id
-N, --app-name TEXT App name
-P, --app-package-name TEXT App package name
-h, --help Show this message and exit
./acdt play-store-publish -h
Usage: commandline play-store-publish [OPTIONS]
Publish app on the play store
Options:
-c, --credentials-p12 PATH Credentials p12 file
-i, --service-account-id TEXT Service account id
-N, --app-name TEXT App name
-P, --app-package-name TEXT App package name
-V, --app-version TEXT App version
-K, --apk PATH APK file
-T, --track [alpha|beta|production]
Set track (alpha / beta / production)
-R, --release-notes PATH Release notes folder
-h, --help Show this message and exit
You can specify release notes in text files for each locale, or each language or a default one for all your languages.
First level must be the language code and second level must be the country code.
A default file named default.txt can be defined at each level.
A version file named <app-version>.txt can also be defined at each level. The filename should exactly match the version set as parameter --app-version to be considered.
Release notes files are selected in this order:
- Looking for corresponding version file in the country folder
- Fallback on the default file in the country folder
- Fallback on the version file in the language folder
- Fallback on the default file in the country folder
- Fallback on the version file at the top-level
- Fallback on the default file at the top-level
changelogs
├── default.txt
├── en
│ ├── AU
│ │ └── default.txt
│ ├── GB
│ │ ├── default.txt
│ │ └── v1.1.0.txt
│ ├── US
│ └── default.txt
├── fr
│ ├── CA
│ ├── FR
│ │ └── v1.1.0.txt
│ ├── v1.0.0.txt
└── v1.0.0.txtConsidering the tree above, the release notes for the version v1.1.0 will be:
- en-AU: changelogs/en/AU/default.txt
- en-GB: changelogs/en/GB/v1.1.0.txt
- en-US: changelogs/en/default.txt
- fr-CA: changelogs/default.txt
- fr-FR: changelogs/fr/FR/v1.1.0.txt
./acdt gitlab-create-release -h
Usage: commandline gitlab-create-release [OPTIONS]
Create gitlab release
Options:
-u, --url TEXT Gitlab url
-t, --access-token TEXT Your Gitlab access token
-p, --project-id TEXT Your Gitlab project id
-T, --tag-name TEXT Tag name associated to the release
-N, --release-name TEXT Release name
-D, --release-description VALUE Release description
-M, --release-milestone TEXT Milestone associated to the release, if
several separated by semicolon
-h, --help Show this message and exit
./acdt gitlab-update-release -h
Usage: commandline gitlab-update-release [OPTIONS]
Update gitlab release
Options:
-u, --url TEXT Gitlab url
-t, --access-token TEXT Your Gitlab access token
-p, --project-id TEXT Your Gitlab project id
-T, --tag-name TEXT Tag name associated to the release
-N, --release-name TEXT Release name
-D, --release-description VALUE Release description
-M, --release-milestone TEXT Milestone associated to the release, if
several separated by semicolon
-h, --help Show this message and exit
./acdt gitlab-delete-release -h
Usage: commandline gitlab-delete-release [OPTIONS]
Delete gitlab release
Options:
-u, --url TEXT Gitlab url
-t, --access-token TEXT Your Gitlab access token
-p, --project-id TEXT Your Gitlab project id
-T, --tag-name TEXT Tag name associated to the release
-h, --help Show this message and exit
./acdt gitlab-close-milestone -h
Usage: commandline gitlab-close-milestone [OPTIONS]
Close gitlab milestone
Options:
-u, --url TEXT Gitlab url
-t, --access-token TEXT Your Gitlab access token
-p, --project-id TEXT Your Gitlab project id
-N, --milestone-name TEXT Milestone name
-h, --help Show this message and exit
./acdt changelog-generate -h
Usage: commandline changelog-generate [OPTIONS]
Generate changelog
Options:
-R, --release-notes PATH Release notes folder
-V, --version TEXT Version
-F, --output-format [MARKDOWN|JSON|XML]
Set output format (Default MARKDOWN)
-h, --help Show this message and exit
Changelog is generated from a release notes folder which must be structured like for play-store-publish command. But unlike for play-store-publish command, changelog-generate command considers only folders containing version.txt file and ignores default.txt files.
./gradlew run : run main class
./gradlew distZip : generate zip release: build/distributions/acdt-0.2.0.zip
./gradlew distTar : generate zip release: build/distributions/acdt-0.2.0.tar
./gradlew installDist : generate runnable executable: build/install/acdt/bin/acdt
Docker acdt image
acdt (Android Continuous Delivery Tools) project is a toolset to continuous delivery for Android app.
docker build -t docker-acdt .
docker run -it -d --name docker-acdt docker-acdt
docker exec -it docker-acdt /bin/bash
acdt is installed in folder /opt/acdt/acdt-0.2.0 so you can run acdt with this command: /opt/acdt/acdt-0.2.0/bin/acdt -h