Migration from Bintray
Bintray was, in its heyday, a popular open-source hosting service for storing Java libraries, packages, and components. The IntelliJ IDEA team had been using it actively to maintain our artefacts. JFrog, the company that owns Bintray, announced this year the end of an era – Bintray will be riding off into the sunset on May 1, 2021. Since April 1, we have had read-only access to our repos.
This blog will give you a quick overview of how we have migrated from Bintray and what we have done to make sure the process will be as painless as possible for you.
As soon as we learned the news, we worked to find a solution that would guarantee a fast, secure, and transparent transition. The obvious first answer that came to mind was to use JetBrains Space.
We have now migrated all the Bintray artefacts required for IntelliJ IDEA to Space with our custom scripts. Now, we are publishing our Maven artefacts that were previously stored in Bintray to Space Packages.
How did we do it?
In the existing Space project, we opened the packages page to create a new repository specifying its name, type, and access rights. Once we created the repository, we chose the desired build system, copied the code from the tabs to our build script, and deleted the existing bintray usages from it. That’s it!
To learn more about Space packages, you can read this series of blog posts.
For our JetBrains Runtime artefacts, we used AWS S3.
Will this affect you?
There are remaining Bintray usages, as the migration process is still ongoing – Though it is going smoothly. We suggest upgrading to version 2020.3 and above to avoid any unexpected errors.
And of course, please report any issues you have to our issue tracker.