Update Windows CI build Mandrel version?

[gsmet]

Our Windows CI build is still using Mandrel for Java 17 AFAIK:

      - name: Setup GraalVM
        id: setup-graalvm
        uses: graalvm/setup-graalvm@v1
        if: startsWith(matrix.os-name, 'windows')
        with:
          version: 'mandrel-latest'
          java-version: '17'
          components: 'native-image'
          github-token: ${{ secrets.GITHUB_TOKEN }}

See https://github.com/quarkusio/quarkus/blob/main/.github/workflows/ci-actions-incremental.yml#L905-L913

I have also seen some 404 failures when the action is run so I'm wondering if it needs further adjustments?

Also, I think I had some issues with this in old branches as I couldn't find a way to use graalvm/setup-graalvm@v1 and point to the older Mandrel version we wanted to use.

Maybe the Mandrel team already solved this and can help?

[quarkus-bot]

/cc @Karm (mandrel), @galderz (mandrel), @zakkak (mandrel)

[zakkak]

I have also seen some 404 failures when the action is run so I'm wondering if it needs further adjustments?

If not persistent it could be some GH network issue, AFAIK the action just downloads the releases from github and installs them in the GH runner instance.

Also, I think I had some issues with this in old branches as I couldn't find a way to use graalvm/setup-graalvm@v1 and point to the older Mandrel version we wanted to use.

Maybe the Mandrel team already solved this and can help?

Sure, I will have a look.

[zakkak]

I have also seen some 404 failures when the action is run so I'm wondering if it needs further adjustments?

Tracked in setup-graalvm repository: graalvm/setup-graalvm#64

Also, I think I had some issues with this in old branches as I couldn't find a way to use graalvm/setup-graalvm@v1 and point to the older Mandrel version we wanted to use.

Yes, that's because we use mandrel-latest, so 3.2 which should be using Mandrel 23.0 tries to fetch 23.1... When creating a release branch we should switch from mandrel-latest to the actual version we are interested in. One issue with this is that we can't (at the moment) say version: 23.0 and have setup-graalvm fetch the latest 23.0.x release, at the moment we need to use the exact version, e.g. mandrel-23.0.1.2-Final.

[gsmet]

This has been somehow sorted out by @zakkak so we can close this one. If it needs further refinements, we probably need a new issue with a better title.

[zakkak]

FTR this was fixed in graalvm/setup-graalvm#67

We still can't define version as 23.0 and have setup-graalvm fetch the latest 23.0.x release, but at least we can use mandrel-latest and set the java-version to get the latest mandrel build based on that java-version.