From 50ca1482f31f5710ae24fb9eeec1508bc7a96dfd Mon Sep 17 00:00:00 2001
From: Drew Hamilton <github@drewhamilton.dev>
Date: Tue, 14 Jan 2025 07:28:43 -0800
Subject: [PATCH] Separate build and test steps in CI (#468)

I'm curious about how much time each takes separately. I'd also ideally like to trigger the sample build(s) after the "Upload MavenLocal directory" step completes, but that's not currently possible in GitHub Actions.
---
 .github/workflows/ci.yml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index f6fa636d..ae5aa831 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -21,10 +21,11 @@ jobs:
         uses: gradle/actions/setup-gradle@v4
 
       - name: Build
-        run: ./gradlew build publishToMavenLocal --stacktrace
+        run: ./gradlew :poko-annotations:build :poko-compiler-plugin:build :poko-gradle-plugin:build publishToMavenLocal --stacktrace
         env:
           ORG_GRADLE_PROJECT_personalGpgKey: ${{ secrets.ORG_GRADLE_PROJECT_personalGpgKey }}
           ORG_GRADLE_PROJECT_personalGpgPassword: ${{ secrets.ORG_GRADLE_PROJECT_personalGpgPassword }}
+
       - name: Upload MavenLocal directory
         uses: actions/upload-artifact@v4
         with:
@@ -32,6 +33,10 @@ jobs:
           path: ~/.m2/repository/dev/drewhamilton/poko/
           if-no-files-found: error
 
+      - name: Test
+        # Builds and run tests for any not-yet-built modules, i.e. the :poko-tests modules
+        run: ./gradlew build --stacktrace
+
   test-with-jdk:
     runs-on: ubuntu-latest
     strategy: