Now changed to:

<Error>
  <Code>NoSuchBucket</Code>
  <Message>The specified bucket does not exist</Message>
  <BucketName>jruby.org</BucketName>
  <RequestId>56E1BAF720C199DC</RequestId>
  <HostId>KhnJdpbgYY+6WXWMj8Zi42GWfLcN69bMknK642D686rY2rwgI/1/1W60Lcgj7z2EE88ynSlddEU=</HostId>
</Error>

This is affecting Logstash Travis CI tasks.

@headius @enebo
Please look into this as soon as you can. I'd be most appreciative.

Related: URLs for artifacts on all of the versions listed on http://jruby.org/files/downloads/ end up emitting HTTP 404 Not Found.

all downloads from https://s3.amazonaws.com/jruby.org/* are impacted by this

confirmed - none work e.g. anything from 9.2.0.0 http://jruby.org/files/downloads/9.2.0.0/index.html

it seems everything moved to maven, example: https://repo1.maven.org/maven2/org/jruby/jruby-dist/9.1.13.0/jruby-dist-9.1.13.0-bin.tar.gz

Seems like our travis builds are broken

https://travis-ci.org/igrigorik/http-2/jobs/399058240

https://travis-ci.org/socketry/nio4r/jobs/390765726

Does RVM need to be updated?

It looks like the JRuby team asked RVM to change their links to Maven on Nov 9, 2017 but the issue stalled and I can't find a PR on RVM that would fix this.

Damn, that's frustrating.

Ugh...it sounds like the bucket was removed again. We'll get it restored today.

@headius should we see the maven repo url as the right/official/futureproof place to get jruby from?

@jsvd yeah maven was intended to be the replacement and it happened for rbenv but we did not realize rvm has not updated to it yet.

also, while the jruby download frontpage links use maven, the download pages themselves still use s3: http://jruby.org/files/downloads/9.2.0.0/index.html

In process of re-uploading all releases 9.2.0.0 and 9.1.17.0 are back up so those should be working again.

@jsvd Yeah those files just need to be patched to use maven locations.

index files should largely be updated. This involved a script but all the normative urls for -bin,-src,-complete all now point at maven instead of s3 (for 1.7.26, 9.1+ as those are only -dist releases we have made). Older pre jruby-dist builds still point at s3.

We shall leave this open a day or two in case I did not restore something or made an error editing those link files. I have an issue opened about our bucket getting deleted again and the resolution may be added here for posterity.

In any case, today ended up making all ruby managers point to new source and as people update those managers our dependence on s3 will be for history and windows exes (which will enter maven soon -- knock on wood).

@enebo Thank you for the above info. We recently upgraded to 1.7.27 on windows to gain TLSv1.2 support for access to rubygems. In doing so we're running into the issue described here in 3920

So - We've been on the hunt for 1.7.24 which may have the TLSv1.2 support we need but without the issue in 3920. (In parallel we're working on a major upgrade to 9k series if it doesn't pan out). While looking for 1.7.24 for windows x64, we discovered the missing S3 downloads and subsequently that maven doesn't have windows versions just yet.

Is there another way at this point to find this version?

Thank you kindly!

https://s3.amazonaws.com/jruby.org/downloads/1.7.27/jruby_windows_x64_1_7_27.exe broken

I'm experiencing the same issue today

Old issue that should have been closed. Long story short, we lost most of our S3 downloads when our project host mistakenly removed our buckets from what they thought was a shared account. The archives were restored from another location but the original .exe installers were lost.

Going forward, we will publish the .exe installers to Maven, like we now do for the rest of the archives. We recommend using Maven as the canonical source.

See #4829.