Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Run Gradle setup error after node16 update #153

Closed
mr-fernandez opened this issue Jan 31, 2022 · 6 comments
Closed

Question: Run Gradle setup error after node16 update #153

mr-fernandez opened this issue Jan 31, 2022 · 6 comments

Comments

@mr-fernandez
Copy link

After #144 Im getting the following error while running the GH actions:

[Java CI with Gradle/build] ⭐ Run Setup Gradle
INFO[0040] ☁ git clone 'https://github.com/gradle/gradle-build-action' # ref=v2
[Java CI with Gradle/build] ❌ Failure - Setup Gradle
Error: The runs.using key in action.yml must be one of: [composite docker node12], got node16

Any idea if I can fix this on my end?

@BorzdeG
Copy link

BorzdeG commented Jan 31, 2022

@MRFernandez9 As a temporary solution - roll back to version 2.1.1: gradle/gradle-build-action@v2 > gradle/gradle-build-action@v2.1.1

@mr-fernandez
Copy link
Author

Thanks @BorzdeG !

@bigdaz
Copy link
Member

bigdaz commented Feb 1, 2022

Is this from a run on a GitHub-hosted runner? If so, what is the runs-on: value for the Job?
My understanding was that all runners now shipped with Node 16, but I could be wrong.

@bigdaz
Copy link
Member

bigdaz commented Feb 4, 2022

Closing for now due to lack of response.

@bigdaz bigdaz closed this as completed Feb 4, 2022
@BorzdeG
Copy link

BorzdeG commented Feb 4, 2022

I have an error when running locally through act

Docker: 20.10.12
act: 0.2.25

UPD: Found a related issue: nektos/act#910

@bigdaz
Copy link
Member

bigdaz commented Feb 4, 2022

@BorzdeG Thanks for clarifying. I think I'll stick with node16 in gradle-build-action since support in act is pending.
The workaround to use an earlier release of the action will need to suffice in the interim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants