I have a bamboo plan set up to pull from a bitbucket repository. It builds every time a push is made to the repo. If and only if the plan successfully completes, I want to push the changes (the ones I originally pushed to bitbucket which triggered the plan) to a remote git server.
So far I did the following:
If I set the 'Source Code Checkout' task to 'Force Clean Build' this works and every commit I make is built on the server, then pushed to the remote repository. This is what I want.
However if I don't force a clean build, the first build's push is sent to the remote, but consequent builds are not. If I navigate to the Job's directory (for me /var/atlassian/application-data/bamboo/xml-data/build-dir/<JOB_NAME>) and run 'git status' I get: "HEAD detached at 0631325" - showing the short version of the hash of the latest commit.
I'm not familiar enough with git to understand exactly how to deal with this in an efficient manner. I know pulling the repo again completely to another location would technically work, but I feel that that is unnecessary since to build the plan the repo was pulled already. The files are already there.
Is there a recommended way that I could push the changes from this headless repo to a remote repo, instead of pushing from the outdated origin branch?
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
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!
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