Bintray sunsetting impacting certain pipes

[Joey Benamy]

Per request by Atlassian support, I'm posting this here.  We use the JfrogDev/artifactory-generic-upload pipe in one of our Bitbucket (cloud) repositories.  The pipe is distributed via Bintray, which is being sunset on May 1.  See https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/.  We would like to continue using this pipe after Bintray is sunset.  Is this something the community can help with?

[Vinay Aggarwal]

Hello Joey, 

I am Vinay Aggarwal from JFrog. My team was managing old pipes which are being deprecated.

The pipe in question is https://bitbucket.org/JfrogDev/artifactory-generic-upload/src/master/

This pipe is being deprecated in favor of new pipe, which is located here https://bitbucket.org/jfrog/jfrog-setup-cli/src/master/ . This new pipe can do everything that artifactory-generic-upload can do and much more. It can upload any artifact to any repo type, can even scan using Xray and works with all other JFrog products. Because it is using JFrog CLI in the background, it is also being kept up to date with product features. So it is truly a better solution which is more flexible and maintained better.

So can you see if you can migrate to new pipe?

[Joey Benamy]

Thanks for that information.  I will try to switch the build pipeline for this repo from artifactory-generic-upload to jfrog-setup-cli.

[Vinay Aggarwal]

That is great news. Thanks for sharing.

[Joey Benamy]

It is working with the jfrog-setup-cli pipe.  Thanks!