I'm failing at the first hurdle with a new install of Bamboo.
I have a Atlassian Stash server running in EC2. I am trying to add one of the project repo's to my fresh Bamboo (hosted) install, but when the build runs, I get:
<project> : Plan 'COOP-BUIL' could not be started. Exception: java.lang.RuntimeException: com.atlassian.bamboo.repository.RepositoryException: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/bin/git ls-remote http://<user>:<scm host>/scm/cop/source.git failed with code 128. Working directory was [.]., stderr: [error: The requested URL returned error: 403 while accessinghttp://<user>:********@<scm host>/scm/cop/source.git/info/refs?service=git-upload-pack, fatal: HTTP request failed]
Also, when I click "view error log" I get what seems to be a binary file (see screenshot).
Screen Shot 2015-02-22 at 11.14.14.png
I'm moving away from our Jenkins CI server to Bamboo because I hoped it would be easier. But doesn't seem to be at the moment.
Any help gratefully received.
More about error log problem here: https://answers.atlassian.com/questions/12159050.
About repository - do you use local, remote or elastic agent? Also what operating system is server and agent using?
There are two moments when Bamboo needs access to repository. On server for change detection and on agent for actual build. Seeing actual stack trace with error would help diagnosing what's wrong.
One thing you could try - accessing some public git repository (like on github) just to see if that works.
Hi Peter Thanks for your email. I've worked it out. It seems Bamboo can't connect to a Git repo via HTTP on any other port except 80 or 443. Stash by default runs on 7990, so i've setup a reverse proxy to get it to work on 80. I kind of feel I should have spotted this earlier, but hopefully Atlassian can update their documentation on this. Thanks for your help though.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
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