search

nus-cs2103-AY2223S2 / forum

12 stars 0 forks source link

Gradle CI workflow dependency library is down #292

Closed heeeyi closed 1 year ago

heeeyi commented 1 year ago

Hi I have recent push on Github, which was failed reporting error "Could not HEAD ". Received status code 503 from server: Service unavailable. This is the screenshot:

image

When I tried to follow the link for the last failed jar file, the webpage shows 404 error. Therefore, this resource is genuinely missing. In this case, how are we suppose to do our CI/CD workflow check, or should we just bypass it?

image

ShiJiaAo commented 1 year ago

I was getting the same issue too. Looks like it's a gradle problem and I believe you can check the status here: https://status.gradle.com/

It seems like these timeouts are random. I just kept redoing the test and it worked eventually.

damithc commented 1 year ago

I was getting the same issue too. Looks like it's a gradle problem and I believe you can check the status here: https://status.gradle.com/

It seems like these timeouts are random. I just kept redoing the test and it worked eventually.

Thanks for sharing this @ShiJiaAo Seems to be back to normal now.