How can you include the git folder in a Bamboo Artifact?

We have 3 stages, build, test, deploy in our bamboo plan. The first stage creates an artifact with the pattern **/*

That copies .files and .folders just fine except for .git which I'm guessing comes from http://ant.apache.org/manual/dirtasks.html default excludes

We require the git folder to deploy to heroku via

git push heroku-remote master

Any suggesstions/workarounds? Should I just copy or rsync locally from my ../{project}-BUILD/.git/ folder?

5 answers

1 accepted

Accepted Answer
2 votes

I successfully copied the .git folder with this pattern

1) Create definition

2) in "Name" what you want

3) in "location" the relative path PLUS .git (so for example I put ".git" because it is in the root of my project)

4) in "copy pattern" put "**"

.. finally I get a new directory with all the git files inside!

The problem I have is that I cannot include the .gitignore files!

Have you made any further progress on this - I am in a similar situation and have managed to copy the .git folder along with my checked out source as you describe but losing the .gitignore is causing problems! A suggestion on another Atlassian Answer is to zip the entire folder and publish the zip as an artifact. This seems a bit over the top for something that seems a relatively basic feature of a CI system.

We used Michele's approach for .git folder, but for .gitignore we renamed the file to gitgnore at last step of build stage and in deployment project we renamed it again to .gitignore just after artifact download task.

There should be an option not to ignore hidden files in artifact definition...

Just to add to this, I get permission denied when trying to copy the .git folder from the bamboo.buildKey folder on the .pack and .idx files, all other git files copy just fine

Just to give a hint, I think it is related to this:

http://ant.apache.org/manual/dirtasks.html#defaultexcludes

Any way to override the default excludes in Ant? Documentation says the following, but don't see any corresponding bamboo config:

defaultexcludes="no"

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Monday in Jira Ops

Jira Ops Early Access Program Update #1: Announcing our next feature and a new integration

Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...

344 views 0 8
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