Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,868
Community Members
 
Community Events
176
Community Groups

Bintray sunsetting impacting certain pipes

Edited

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?

1 comment

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?

Like # people like this

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

Like Vinay Aggarwal likes this

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

That is great news. Thanks for sharing.

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events