Running Bamboo Plan to populate repository

Question

I am trying to generate a bamboo plan that would populate the Bitbucket repository.

I have created a shell script, that basically runs the git commands in a sequence.  When it comes to below two commands, I get an error

* git pull origin master
* git push -u origin master

fatal: could not read Password for 'https://myuserid@git-devserver.company.com': No such device or address

fatal: could not read Password for ''https://myuserid@git-devserver.company.com': No such device or address

Prior to this, I have a command in the script for

* git config http.sslVerify "false"

The sequence of my steps is as below

* git init
* git add --all
* git commit -m "initial commit"
* git config http.sslVerify "false"
* git remote add origin 'https://myuserid@git-devserver.company.com
* git remote -v

The above steps work fine.

This is where I get the above errors

* git pull origin master

* git push -u origin master

Charlie Misonne · Answer

Strange

Are you sure your url is correct? It doesn't look like a Bitbucket url

It should look like this:  http://myuserid:mypassword@git-devserver.company.com/scm/yourprojectkey/yourreponame.git When you go to your Bitbucket repo via the browser you'll find a Clone menu item in the sidebar. Copy the http variant to your clipboard and don't forget to add the password.
Hope that helps

ABA · Answer

I want to set-up ssh, but encountering some resistance here for creating ssh for the user that runs bamboo.  So, in the meantime, I tried the other suggestion you made userid:password for the remote call but now I get repository https://myuserid:mypassword@git-devserver.company.com not found.

What else do I need to do to get this moving further?

ABA · Answer

Sorry, if I appear to be completely clueless about it.

I was getting a similar password error before executing this command

git remote add origin 'https://myuserid@git-devserver.company.com

So, I added

git config http.sslVerify "false"

and that error went away.  I was thinking that the same config change would take care of the error for

git pull origin master
git push -u origin master