Build improvements

[adangel]

This contains three changes:

• build against 2023.3 as recommended. 2023.3 (233) is the oldest supported version
  @jborgers you changed this in ba4c03b - I assume by accident?
• Disable caching for the verify job.
  This is a follow up on New release 2.0.4 not available #221. Hopefully, the future releases run smoothly then.
• The property pluginVerifierIdeVersions was not used. The IDE versions to test against are determined automatically based on platformVersion (recommended()). With platformVersion=2023.3, verifyPlugin will execute verification against 2023.3.x, 2024.1.x, 2024.2.x, 2024.3.x, 2025.1.x and 2025.2.x. These are right now 6 versions, with each consuming at least 3GB we are already at 18GB... I guess, once 2025.2 is released, we should drop support for 2023.3.

Some background info on the caching problem: A similar problem is described in JetBrains/intellij-platform-plugin-template#462 . We could do the suggestion in the last comment and verify only against the earliest and latest release. But it would have the downside, that we might not see any incompatibilities. That's why I prefer to test the whole range.
The action gradle/action/setup-gradle does already much to reduce the cache sizes (see https://github.com/gradle/actions/blob/main/docs/setup-gradle.md#select-which-branches-should-write-to-the-cache ), e.g. caches are only written from the main/master (default) branch and not from pull requests. But pull requests can still benefit from the cache from the default branch.

Note: Verification currently fails due to #238.

[jborgers]

👍
@adangel Something didn't work when building on my side with 2023.3; changing it to 2024.1 solved it.
I propose to only support 3 versions of IntelliJ. This will mean less maintenance work to support all versions, less test/verify time and less memory usage.

[adangel]

I propose to only support 3 versions of IntelliJ. This will mean less maintenance work to support all versions, less test/verify time and less memory usage.

I'd like to keep the 2023.3 compatibility, if possible. I'm working for a customer who is unfortunately stuck for a while on 2023.3...

[jborgers]

@adangel I am curious why they are stuck?
I just tested the plugin with PR #246 in 2023.3 and it works :-)

[adangel]

@adangel I am curious why they are stuck?

I don't know exactly. It's a combination of priorities and effort. E.g. they need to find and verify the flags to prevent IntelliJ from calling home (which won't work in the corporate network anyway).

I just tested the plugin with PR #246 in 2023.3 and it works :-)

Thanks!