https://gradle.com/ logo
Join Slack
Powered by
This message was deleted.
# community-support
s
This message was deleted.
a
If that is the case, it's possible that repository is not accessible one way or another, so Gradle will try the next repository. But you can also set the filtering: https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:repository-content-filtering
m
Apparently JFrog started redirecting JCenter to Maven Central. Many artifacts are missing.
👀 1
🤯 2
e.g:
Copy code
curl -vv <https://jcenter.bintray.com/org/ysb33r/gradle/grolifant/0.17.0>
< HTTP/1.1 301 Moved Permanently
< Location: <https://repo1.maven.org/maven2/org/ysb33r/gradle/grolifant/0.17.0>
that's breaking all our builds 🤦‍♂️
l
v
What the ... o_O
m
😞 My resolution for the time being was to find another repo that had the artifact that was missing and add manual override of the pluginManagement/repositories - it is really ugly, but works or the moment
I guess jCenter was set to be read-only back in 2021 😕
v
Yes, it was
m
Its annoying because some versions of dependencies exist only in JCenter 😞
v
Yes, annoying like every of the past JCenter outages. One point of why I would have never used it for serious publishing. 🙂
c
If this is really the end of jCenter are Gradle going to commit to sourcing and hosting the missing artifacts, or should those of us with affected builds start trying to fix things directly? I would imagine 8 hours is enough to know if JFrog care to fix anything this time, even if it’s not enough to actually fix it?
v
I'm pretty sure that this was not intentional. I personally am not going to change anything for the builds not working currently.
c
yeah… I’m holding until at least Monday unless I hear otherwise… but if it was accidental you would imagine JFrog would have made a mea culpa statement by now.
v
Why? They also never did that for the regular outages they had in the past. At least not that I recognized it. 😄
c
Hanlon’s razor in action… maybe? To me a 301 redirect seems much more like intentionally taking the off-ramp than their usual neglect/ineptitude.
v
Well, my suspicion is, that they wanted to change the forwaring to MC for libs they don't have themselves to be redirects instead so that they do not go through their infrastructure and accidentally was made also for artifacts that are exclusively available on JCenter. But just a guess of course.
s
We've gotten word through back channels that this has been fixed (not sure what/why it changed yet)
I've checked a few URLs, could you check on your side too?
v
Works again, yes
thanks
Copy code
$ http -v -F <https://jcenter.bintray.com/org/ysb33r/gradle/grolifant/0.17.0/grolifant-0.17.0.jar>
GET /org/ysb33r/gradle/grolifant/0.17.0/grolifant-0.17.0.jar HTTP/1.1
Accept: */*
Accept-Encoding: gzip, deflate
Connection: keep-alive
Host: <http://jcenter.bintray.com|jcenter.bintray.com>
User-Agent: HTTPie/1.0.3



HTTP/1.1 200
Accept-Ranges: bytes
Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Cache-Control: public,max-age=3600
Content-Disposition: attachment; filename="grolifant-0.17.0.jar"; filename*=UTF-8''grolifant-0.17.0.jar
Content-Length: 374092
Content-Type: application/java-archive
Date: Fri, 23 Jun 2023 18:37:48 GMT
ETag: 278ef7b9d9b786ed7ff7e99d8f2002f38c5f4678
Last-Modified: Sat, 02 May 2020 09:12:35 GMT
Via: 1.1 google
X-Checksum-Md5: 24cf04b62d7efbad85702f0bbb146f29
X-Checksum-Sha1: 278ef7b9d9b786ed7ff7e99d8f2002f38c5f4678
X-Checksum-Sha256: 3c9f99effe32c4718f73cb538ca1aaad4fd84a99c14104b5abe6d35a22043843



+-----------------------------------------+
| NOTE: binary data not shown in terminal |
+-----------------------------------------+
s
I think we're still going to put out some more communication about this. We were doing an analysis to see how many plugins were dependent on JCenter-only artifacts
❤️ 1
c
for completeness… working here too.
👌 1
9 Views
Open in Slack
PreviousNext
Powered by