jdeploy.yml

# This workflow builds the Java project with Maven and publishes native app installers to
# GitHub Releases via jDeploy (https://www.jdeploy.com).
#
# Flow: push to develop -> job 1 tags "1.0.<commit count>" -> tag push -> job 2 builds + publishes.
# The tag is required: the jDeploy action only creates a versioned release for tag pushes. On a
# branch push it instead publishes a rolling prerelease named after the branch at version
# "0.0.0-<branch>".
#
# Needs the ADM_JDEPLOY_GITHUB_TOKEN secret (a personal access token with contents:write).
# See README.md -> "Releasing" for how to create it.

name: build and deploy using jDeploy

on:
  push:
    branches: ['develop']
    # IMPORTANT: only version tags - must NOT match 'jdeploy'. jDeploy creates a tag by that name
    # in this repo to hold package-info.json, and 'tags: [*]' would re-trigger this workflow on it,
    # publishing a bogus release with version "jdeploy" and pointing dist-tags.latest at it.
    tags: ['1.0.*']
    # NOTE: path filters are ignored for tag pushes, so this only skips job 1
    paths-ignore:
      - 'README.md'
  workflow_dispatch:

concurrency:
  group: jdeploy-release-${{ github.repository }}
  cancel-in-progress: false

# needed to create tags and releases
permissions:
  contents: write

jobs:
  # ==========================================
  # JOB 1: tag on merge to develop
  # ==========================================
  tag-release:
    if: ${{ github.event_name == 'workflow_dispatch' || github.ref == 'refs/heads/develop' }}
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          # CRITICAL: must use a PAT here. Pushes made with the default GITHUB_TOKEN don't
          # trigger workflows, so the 'build-and-deploy' job below would never run.
          token: ${{ secrets.ADM_JDEPLOY_GITHUB_TOKEN }}
          fetch-depth: 0

      - name: Get Version and Push Tag
        run: |
          COMMIT_COUNT=$(git rev-list --count HEAD)
          VERSION="1.0.${COMMIT_COUNT}"

          echo "Calculated version: $VERSION"

          if git rev-parse "$VERSION" >/dev/null 2>&1; then
            echo "✅ Tag $VERSION already exists. No new release needed."
          else
            echo "▶ Creating and pushing new tag: $VERSION"
            git config user.name "GitHub Actions Bot"
            git config user.email "<>"
            git tag "$VERSION"
            git push origin "$VERSION"
          fi

  # ==========================================
  # JOB 2: build and deploy (triggered by tag)
  # ==========================================
  build-and-deploy:
    # second guard against publishing jDeploy's own metadata tag as if it were a release
    if: ${{ github.ref_type == 'tag' && github.ref_name != 'jdeploy' }}
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          # full history so gen_release_notes.sh can log commits back to the previous tag
          fetch-depth: 0

      - name: Set up JDK 22
        uses: actions/setup-java@v4
        with:
          java-version: '22'
          distribution: 'temurin'
          cache: maven

      - name: Build with Maven
        # pass the tag in as the version so app.properties matches the release
        run: mvn -B package --file pom.xml -Drevision=${{ github.ref_name }}

      # publishes to https://github.com/jpage4500/AndroidDeviceManager/releases
      # - uploads mac/windows/linux installers as release assets
      # - updates package-info.json on the 'jdeploy' tag (used by installed apps to auto-update)
      - name: Publish release to GitHub
        uses: shannah/jdeploy@master
        with:
          github_token: ${{ secrets.ADM_JDEPLOY_GITHUB_TOKEN }}
          deploy_target: 'github'

      # also attach the fat jar - see SERVER.md for running ADM headless
      # NOTE: uploaded with the CLI (not an action) so the release body jDeploy just wrote is left alone
      - name: Attach jar to release
        env:
          GH_TOKEN: ${{ secrets.ADM_JDEPLOY_GITHUB_TOKEN }}
        run: |
          gh release upload "${{ github.ref_name }}" target/AndroidDeviceManager.jar \
            --repo "${{ github.repository }}" --clobber

      - name: Generate Release Notes
        env:
          # only used to look up PR titles for merge commits; read-only access is enough
          GITHUB_TOKEN: ${{ github.token }}
        run: |
          chmod +x scripts/gen_release_notes.sh
          ./scripts/gen_release_notes.sh "pr" "brief" > notes.raw

          # drop blank lines and empty-subject commits, then normalize to "- " markdown bullets
          grep -v '^[[:space:]]*$' notes.raw \
            | grep -viE '^[[:space:]]*-?[[:space:]]*no message[[:space:]]*$' \
            | sed -E 's/^[[:space:]]*-[[:space:]]*//; s/^/- /' > release-notes.txt

          if [[ ! -s release-notes.txt ]]; then
            echo "- no changes" > release-notes.txt
          fi

          echo "Generated Release Notes:"
          cat release-notes.txt

      # view releases here: https://github.com/jpage4500/AndroidDeviceManager/releases
      # jDeploy already wrote the installer download links into the body - keep them and add
      # the release notes above
      #
      # IMPORTANT: --draft=false is required. jDeploy uploads tag releases via
      # xresloader/upload-to-github-release, which defaults draft=true and jDeploy never overrides
      # it - so the release is created hidden and its assets 404 for the launcher.
      - name: Publish GitHub Release with notes
        env:
          GH_TOKEN: ${{ secrets.ADM_JDEPLOY_GITHUB_TOKEN }}
        run: |
          EXISTING=$(gh release view "${{ github.ref_name }}" \
            --repo "${{ github.repository }}" \
            --json body -q '.body' || echo "")

          # if the body couldn't be read, fall back to the installer links jdeploy generated
          INSTALLER_LINKS=./jdeploy/github-release-files/jdeploy-release-notes.md
          if [[ -z "$EXISTING" && -f "$INSTALLER_LINKS" ]]; then
            EXISTING=$(cat "$INSTALLER_LINKS")
          fi

          { echo "## Release Notes"; echo ""; cat release-notes.txt; echo ""; echo "$EXISTING"; } > combined-notes.txt

          gh release edit "${{ github.ref_name }}" \
            --notes-file combined-notes.txt \
            --draft=false \
            --latest \
            --repo "${{ github.repository }}"