[Build] Always run Eclipse at the storage-server with Java-21 #2992
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adding a new I-build to the I-build composite seems to not work at the moment and running Eclipse to perform the addition with Java-17 although the Eclipse-SDK/Platform products now require Java-21 could be a cause. A Java-21 JDK was installed via - https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5780
Member
Author
|
Regardless of this change, we should rework all changed locations, sooner rather than later, to run Eclipse locally in Jenkins instead of directly at the storage server. Relates to |
Member
Author
|
The verification build does not test this, thus submitting immediately. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adding a new I-build to the I-build composite seems to not work at the moment and running Eclipse to perform the addition with Java-17 although the Eclipse-SDK/Platform products now require Java-21 could be a cause.
A Java-21 JDK was installed via
I'm not entirely sure the addition started to fail with the latest I-build, but after running the Mark Stable job, modified to use Java-21, it worked. Running it explicitly previously with Java-17 didn't add the build to the composite.
Maybe this was also just a caching issue at the storage-server, but still this change should be applied as we see multiple error messages in the build (but still the build itself didn't fail).