I have setup a Bamboo instance locally to start experimenting with the software and I am trying to get a plan to pull from my organization's GitHub repository.
In the Plan configuration's Source Repositories page, if I put in my username without a password it seems to load all of my public repositories for selection just fine. But if I set a password, it returns with an Invalid Username error and it does not show any repositories.
Is there a step I am missing in configuring Bamboo to load my private organization's repositories?
I contacted support, but they were unable to resolve my particular use case. The guy didn't seem to fully understand the issue as well. But in any case the workaround was to create a second GitHub account and provide it access to the organization's repository that I needed and then use those credentials when using the GitHub connector. Using that account seemed to work fine and I was able to see the repositories I needed.
The only difference between the account that wasn't working and the new one that is, is that the original non-working GitHub account has access to three organizations instead of the one that the new account does. That is the only thing I can think of off the top of my head that would maybe cause the issues.
In either case, this workaround worked for me for the time being. Hope it helps someone else.
Similar problem. Opened ticket BSP-7464
The tech asked me to run the following curl command
curl -u your_username:your_password -X GET http://github.com/api/v2/json/repos/show/your_repo_name
Given that github turned off the v2 API at the beginning of June, I think I see the problem......
Yes, it's fixed in Bamboo 4.1.2. The release is on its way to our content distribution network. If you need access before it's made available on www.atlassian.com, you can use the downloads links below:
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