Use a separate workflow for cutting releases

ctrueden · ctrueden · commit 1b817efe560f · 2023-05-13T09:52:26.000-05:00
Let's not run the mega-melt when cutting a release; just do it.

I made a separate workflow to avoid needlessly restoring and/or saving
the melting-pot cache, which won't be used for the release process.
diff --git a/.github/build.sh b/.github/build.sh
@@ -2,6 +2,11 @@
 curl -fsLO https://raw.githubusercontent.com/scijava/scijava-scripts/master/ci-build.sh &&
 sh ci-build.sh || { echo "Maven build failed. Skipping melting pot tests."; exit 1; }
 
+if [ -f release.properties ]; then
+  # Skip melting pot when cutting a release.
+  exit 0
+fi
+
 # Helper method to get the last cache modified date as seconds since epoch
 last_cache_modified() {
   find "$HOME/.cache/scijava/melting-pot" -type f | while read f
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
@@ -4,8 +4,6 @@ on:
   push:
     branches:
       - master
-    tags:
-      - "*-[0-9]+.*"
   pull_request:
     branches:
       - master
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -0,0 +1,34 @@
+name: build
+
+on:
+  push:
+    tags:
+      - "*-[0-9]+.*"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Java
+        uses: actions/setup-java@v3
+        with:
+          java-version: '8'
+          java-package: 'jdk+fx'
+          distribution: 'zulu'
+          cache: 'maven'
+
+      - name: Set up CI environment
+        run: .github/setup.sh
+
+      - name: Execute the build
+        id: execute-build
+        run: .github/build.sh
+        env:
+          GPG_KEY_NAME: ${{ secrets.GPG_KEY_NAME }}
+          GPG_PASSPHRASE: ${{ secrets.GPG_PASSPHRASE }}
+          MAVEN_USER: ${{ secrets.MAVEN_USER }}
+          MAVEN_PASS: ${{ secrets.MAVEN_PASS }}
+          OSSRH_PASS: ${{ secrets.OSSRH_PASS }}
+          SIGNING_ASC: ${{ secrets.SIGNING_ASC }}
