JCenter & Bintray are going away


Nigel Jones
 

Yesterday JFrog announced their intention to shutdown BinTray and JCenter. Whilst the shutdown is on May 1st, no submissions can occur after the end of February. More at https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/

In Egeria we currently use Azure pipelines for our release process. We build artifacts that are pushed to artifactory, from there to BinTray, on to JCenter & then synced to maven central. This process will therefore break at the end of next month.

I’ve raised an egeria issue to track: https://github.com/odpi/egeria/issues/4664

Also I’ve asked for assistance from the LF team via: https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-21485 (this link is limited to support team)

You can see many other github projects at least impacted in some way by this at: https://github.com/search?p=2&q=jcenter&type=Issues

Our main PR/merge builds pipelines were originally on Azure, but after an extended outage we moved to GitHub actions. This proved relatively easy - decent docs, lots of samples, a thriving community. We now have a better, quicker, simpler & more maintainable process, but haven't yet addressed release.

As part of this challenge my hunch is that moving the same way will be a benefit. I presume many teams will be impacted with this change so hope we can pool ideas and get help from the LF….