Loading GitHub Repo "Invalid Username." Error

[Daniel Dura]

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?

[James Dumay]

Bamboo 4.1.2 is now available from www.atlassian.com

[Marcelo Maidana]

Hi, Do you guys know if this was fixed?

Thanks

Marcelo

[Przemek Bruski]

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:

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2.dmg

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2.tar.gz

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2.tgz

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2.war

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2-windows-x32.exe

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2-windows-x64.exe

https://bamboo-release.s3.amazonaws.com/4.1.2/atlassian-bamboo-4.1.2.zip

These links will be inactivated once the relase appears on www.atlassian.com

[Przemek Bruski]

GitHub disabled the old API. The new one is located at a different host, has different calls and a completely different response format. We hope to introduce support for new GitHub API with Bamboo 4.1.1.

[Andrew Laden]

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......

https://github.com/blog/1090-github-api-moving-on

[Daniel Dura]

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.

[PiotrA]

Daniel,

Any possibility I could ask you for your help in determining the root of the problem? If so, could I ask you to review my comments on your support ticket?

Sorry if I over-nag you :)

[Przemek Bruski]

Which version of Bamboo is it and which protocol? I am guessing it's ssh and Bamboo older than 4.1, right?

If you upgrade to 4.1 or switch to HTTPS protocol, the problem will be gone.

[PiotrA]

Seems to me you're not missing any step and this might be a bug in Bamboo. You should probably contact with http://support.atlassian.com to sort that out.

[Daniel Dura]

Thanks for the sanity check. Ill submit a support request and update this answer with the reply.