Fix GitHub Actions disk space exhaustion by aligning with JetBrains template

[Copilot]

GitHub Actions workflows were running out of disk space. Investigation of the JetBrains IntelliJ Platform Plugin Template revealed configuration gaps that required a two-phase fix.

Changes

Initial Fix

• Add disk space cleanup to build job - Build job downloads 2-3 GB IntelliJ Platform artifacts but lacked the free-disk-space action present in other jobs
• Pin free-disk-space to v1.3.1 - Replace @main with stable release tag across all jobs
• Enable cache-read-only in test/verify jobs - Prevent redundant Gradle cache writes in jobs that run after build

Additional Fix for Verify Job

• Enable aggressive disk cleanup for verify job - Explicitly enable removal of Android SDK (~8 GB), .NET runtime (~1-2 GB), Haskell (~1 GB), Docker images (~2-4 GB), large packages (~4-5 GB), and swap storage (~4 GB) to free up ~20-25 GB total
• Remove deprecated Plugin Verifier IDEs cache - Remove outdated cache configuration that the JetBrains template no longer uses
• Simplify verifyPlugin command - Remove custom home directory parameter to use default IntelliJ Platform Gradle Plugin behavior

# Before - verify job
verify:
  steps:
    - name: Maximize Build Space
      uses: jlumbroso/free-disk-space@main
      with:
        tool-cache: false
        large-packages: false
    - name: Setup Plugin Verifier IDEs Cache
      uses: actions/cache@v5
      with:
        path: ${{ needs.build.outputs.pluginVerifierHomeDir }}/ides
        key: plugin-verifier-${{ hashFiles('build/listProductsReleases.txt') }}
    - name: Run Plugin Verification tasks
      run: ./gradlew verifyPlugin -Dplugin.verifier.home.dir=${{ needs.build.outputs.pluginVerifierHomeDir }}

# After - verify job  
verify:
  steps:
    - name: Maximize Build Space
      uses: jlumbroso/free-disk-space@v1.3.1
      with:
        tool-cache: false
        android: true
        dotnet: true
        haskell: true
        large-packages: true
        docker-images: true
        swap-storage: true
    - name: Run Plugin Verification tasks
      run: ./gradlew verifyPlugin

Original prompt

Could you investigate how the example of jetbrains runs github actions successful while we run out of diskspace...
https://github.com/JetBrains/intellij-platform-plugin-template

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.3.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[mai-space]

@copilot You did well! The build now finishes, but the verify task fails again due to limited disk space

[Copilot]

@copilot You did well! The build now finishes, but the verify task fails again due to limited disk space

I've fixed the verify job disk space issue in commit b753ae9. The changes:

1. Enabled aggressive disk cleanup - Changed large-packages: false to true and explicitly enabled all cleanup options (android, dotnet, haskell, docker-images, swap-storage). This frees up ~20-25 GB.

2. Removed deprecated cache - The JetBrains template no longer uses the Plugin Verifier IDEs cache or custom home directory, which was consuming additional space.

3. Simplified verifyPlugin command - Removed the -Dplugin.verifier.home.dir parameter to use default behavior.

The verify job should now have sufficient disk space to complete successfully.