Reusable workflow for mikbot projects
jobs:
mikbot:
uses: mikbot/mikbot-workflow/.github/workflows/[email protected]
with:
run-maven-publish: true
secrets:
GCP_ACCOUNT_KEY: ${{ secrets.GCP_ACCOUNT_KEY }}
SIGNING_KEY: ${{ secrets.SIGNING_KEY }}
SIGNING_KEY_PASSWORD: ${{ secrets.SIGNING_KEY_PASSWORD }}| Name | Type | Description | Default | Required |
|---|---|---|---|---|
run-maven-publish |
Boolean | Run gradle publish at the end of build |
false | false |
update-plugin-repository |
Boolean | Push plugins to GCS repository | true | false |
update-binary-repository |
Boolean | Push bot binary to GCS repository | false | false |
discord-webhook |
Boolean | Send Gradle Build scan to Discord webhook | false | false |
docker-name |
String | Name for the docker image to publish | null | false |
The following secrets can be specified using GitHub Secrets
| Name | Type | Description | Default | Required |
|---|---|---|---|---|
| BUILDCACHE_USER | String | Gradle Build Cache user | null | false |
| BUILDCACHE_PASSWORD | String | Gradle Build Cache password | null | if BUILDCACHE_USER is specified |
| DISCORD_WEBHOOK | String | Discord Webhook URL to push build scans to | null | if discord-webhook is true |
| GCP_ACCOUNT_KEY | String (base64) | ServiceAccountKey.json of GCS bucket | null | if update-plugin-repository or update-binary-repository is true or run-maven-publish` is true |
| SIGNING_KEY | String | Signing key | null | if run-maven-publish is true |
| SIGNING_KEY_PASSWORD | String | Signing key password | null | if run-maven-publish is true |