CI: fix setup-java ea temurin sigcheck failure - #9611
Conversation
|
looks like that field doesn't do anything. It checks the sig despite it evaluating to false https://github.com/apache/netbeans/actions/runs/34463300876 i guess last resort is action downgrade and pin |
b3f3e20 to
0f517af
Compare
|
still failing. I am out of ideas at this point. Revert workaround and switch vendor? summary of what i tried so far:
|
temurin ea builds don't have a sig file, latest setup-java seems to have an issue too since disabling sig testing didn't work. action downgarade didn't work either - unclear what the cause is lets try to change the JDK vendor while keeping everything else
0f517af to
5a66120
Compare
|
Temporary vendor switch sounds like a good idea. I guess either the Adoptium API or something cached in actions ecosystem is reporting the wrong file hash for that download. I wonder if check-latest and/or force-download work for that file? |
|
will also clear our caches https://github.com/apache/netbeans/actions/caches short before merge. This will rebuild it on master which the other branches can then use. |
|
will change back to temurin when JDK 27 updates from ea to ga. |
setup-java action got updated to 6.01.
and is now failing
whats funny is that the setup-java update is supposed to have a fix for this very issue: actions/setup-java#1260 / https://github.com/actions/setup-java/releases/tag/v6.0.1