[CI] Also deploy maven artefacts for GraalVM CE build #566
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The CI change done in #565 changed the quarkus build to depend on the maven artefacts from the mandrel/graalvm build. It adjusted the mandrel build to produce the maven artefacts, but missed updating the GraalVM CE (or now GraalVM Community) build to do the same. Thus the quarkus build fails, since it wants to download the archived maven repo from the mandrel/graalvm build. This patch should fix it.
Test run with this is here (keeping in draft until that run completes):
https://github.com/jerboaa/graal/actions/runs/6157493384/job/16709008677