App password is used for authentication with remote Bitbucket repositories !!
Here's a similar question
Thanks
No, my question is specific with Yocto build systems. the above link is not related to my query.
for e.g: "git clone https://username:password@bitbucket.org/dir/repo.git", command works, wherein password = "an alphanumeric string created by bitbucket"
if I use the same string in the "SRC_URI" field in the Yocto recipe, I get an error for the password field.
for e.g :"SRC_URI = "git://username:password@bitbucket.org/dir/repo.git;branch=somename;protocol=https;"
Error: "fatal: could not read password for 'https://username@bitbucket.org': No such device or address"
Please advise how to use the bitbucket app password in the SRC_URI field of the Yocto recipe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Instead of your account password, its
e.g :"SRC_URI = "git://username:app-password@bitbucket.org/workspace/repo.git;branch=somename;protocol=https;"
Clone URL is available in your Bitbucket repo and App paasword can be created in your personal settings page
https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The "password" I was referring to in my reply refers to "app-password", which does not work with Yocto recipe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Satish Jadhav Adid you find a solution in the meantime, I have the exact same issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please try this syntax for the SRC_URI
SRC_URI = "git://git@bitbucket.org/myworkspace/myrepo.git;protocol=https;user=myusername:my-app-password;"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.