Add Fabric JAR build and upload steps to CI workflows

Author: renvins

.github/workflows/ci.yml

@@ -3,9 +3,9 @@ name: CI Build and Infrastructure Check
 # Controls when the workflow will run
 on:
   push:
-    branches: [ master ] # Or your default branch (e.g., master)
+    branches: [master] # Or your default branch (e.g., master)
   pull_request:
-    branches: [ master ] # Or your default branch
+    branches: [master] # Or your default branch
 
 jobs:
   # Job to build the plugin and test Docker infrastructure
@@ -37,6 +37,9 @@ jobs:
       - name: Build JAR files
         run: ./gradlew shadowJar
 
+      - name: Build Fabric JAR
+        run: ./gradlew fabric:build
+
       # Upload Bukkit JAR as an artifact
       - name: Upload Bukkit JAR Artifact
         uses: actions/upload-artifact@v4
@@ -55,6 +58,15 @@ jobs:
           retention-days: 14 # Keep artifacts for 14 days
           if-no-files-found: error # Fail the workflow if no JARs are found
 
+      # Upload Fabric JAR as an artifact
+      - name: Upload Fabric JAR Artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: serverpulse-fabric-jar
+          path: fabric/build/libs/*.jar
+          retention-days: 14 # Keep artifacts for 14 days
+          if-no-files-found: error # Fail the workflow if no JARs are found
+
       # --- Infrastructure Testing ---
 
       # 4. Install jq (needed for parsing InfluxDB health check JSON)

.github/workflows/create_release.yml

@@ -33,9 +33,12 @@ jobs:
         uses: gradle/actions/setup-gradle@v4 # Use v4 or latest stable version
 
       # Gradle with the new updates doesn't support arguments
-      - name: Build jar
+      - name: Build Bukkit and Velocity jar
         run: ./gradlew shadowJar
 
+      - name: Build fabric jar
+        run: ./gradlew fabric:build
+
       # 5. Find the Bukkit Shadow Jar file and extract its name
       - name: Find Bukkit Shadow Jar and Extract Name
         id: find_bukkit_jar
@@ -68,7 +71,23 @@ jobs:
           echo "filename=$JAR_FILENAME" >> $GITHUB_OUTPUT
         shell: bash
 
-      # 7. Upload the Bukkit Shadow Jar as a release asset
+      # 7. Find the Fabric Jar file and extract its name
+      - name: Find Fabric Jar and Extract Name
+        id: find_fabric_jar
+        run: |
+          JAR_PATH=$(find fabric/build/libs -maxdepth 1 -name '*.jar' -printf "%s %p\n" | sort -nr | head -n 1 | awk '{print $2}')
+          if [ -z "$JAR_PATH" ]; then
+            echo "Error: Could not find the shadow JAR file in fabric/build/libs/"
+            exit 1
+          fi
+          JAR_FILENAME=$(basename "$JAR_PATH")
+          echo "Found JAR path: $JAR_PATH"
+          echo "Found JAR filename: $JAR_FILENAME"
+          echo "path=$JAR_PATH" >> $GITHUB_OUTPUT
+          echo "filename=$JAR_FILENAME" >> $GITHUB_OUTPUT
+        shell: bash
+
+      # 8. Upload the Bukkit Shadow Jar as a release asset
       - name: Upload Bukkit Release Asset
         uses: svenstaro/upload-release-action@v2
         with:
@@ -78,12 +97,22 @@ jobs:
           tag: ${{ github.ref }} # The git tag associated with the release that triggered the workflow
           overwrite: true # Optional: Replace asset with the same name if it already exists
 
-      # 8. Upload the Velocity Shadow Jar as a release asset
+      # 9. Upload the Velocity Shadow Jar as a release asset
       - name: Upload Velocity Release Asset
         uses: svenstaro/upload-release-action@v2
         with:
           repo_token: ${{ secrets.GITHUB_TOKEN }} # Provided by GitHub Actions automatically
           file: ${{ steps.find_velocity_jar.outputs.path }} # The path to the JAR found in the previous step
           asset_name: ${{ steps.find_velocity_jar.outputs.filename }} # Use the filename extracted earlier
           tag: ${{ github.ref }} # The git tag associated with the release that triggered the workflow
+          overwrite: true # Optional: Replace asset with the same name if it already exists
+
+      # 10. Upload the Fabric Jar as a release asset
+      - name: Upload Fabric Release Asset
+        uses: svenstaro/upload-release-action@v2
+        with:
+          repo_token: ${{ secrets.GITHUB_TOKEN }} # Provided by GitHub Actions automatically
+          file: ${{ steps.find_fabric_jar.outputs.path }} # The path to the JAR found in the previous step
+          asset_name: ${{ steps.find_fabric_jar.outputs.filename }} # Use the filename extracted earlier
+          tag: ${{ github.ref }} # The git tag associated with the release that triggered the workflow
           overwrite: true # Optional: Replace asset with the same name if it already exists