Copy repository into another project

In Bitbucket Server, I know there's a way to move repos from one project to another existing project. But is there a way to copy the repo to another existing project? It would preserve the old repo while making newer changes to the copy. 

4 answers

1 accepted

1 vote

You could just fork the repository into another project. See Using forks in Bitbucket Server

Thank you. This seems to be the easiest way to copy a repo to another project. 

1 vote

Hi Kevin,

You can do this using ScriptRunner for Bitbucket Server. Once installed you can go to Admin -> ScriptRunner -> Built-in scripts -> Clone a repository.

This will clone an existing repository to any project you choose. You can see the documentation here.

Let us know how you get on with that or if you need further help.

Thanks,
Adam 

This seems like a useful tool, but I was hoping to find a free, built-in way to do this. Thanks for the tip!

1 vote

Hi @Kevin Thomas,

As of Bitbucket Server 4.9, we provide a repository import feature. You could use this to copy one repository into another project.

See https://confluence.atlassian.com/bitbucketserver/importing-code-from-an-existing-project-776640909.html#Importingcodefromanexistingproject-Importcodeusingthewebinterface for more details

Hope this is what you're looking for,

Kristy

Thanks, I've tried doing this already. It works, but it takes some time to import.

I choose 'Git' as my 'Import from' option and give it the link to the repo I want to clone. I would think there should be a way to 'import from another project' but I realize that's what forking is for. 

Thanks for the tip, though!

The easiest way:

  • Clone your repository to your local machine
  • Create a new repository on Bitbucket (within your desired project)
  • Setup the new Bitbucket-repository as a remote repository within your local repository
  • Push the local repository to the new repository ....

That's it - or did I misunderstood your question?

I'm aware of this method and it's what I was going to do but I consider it the "brute force" method smile. I'm going to do it this way if I can't find a simpler way to do it through the GUI.

Problem is, we have about 30 repos in one project. We're recompiling them to a newer framework and keeping track of them in a new project. If there's an easy way to do it through the interface itself, I'd rather do that. 

"Why don't you just recompile them and push them back to the original repositories, maybe tag the commits or create a branch?" I wish I made the rules...but our team wants access to both sets of code.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,764 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you