From: "Altous, Salahaldeen" <Salahaldeen.Altous@leica-camera.com>
To: "Janne Kiiskila" <janne.kiiskila@izumanetworks.com>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] Http access token fetching with gitsm fetcher
Date: Sun, 21 Apr 2024 23:52:51 -0700 [thread overview]
Message-ID: <28950.1713768771510530708@lists.yoctoproject.org> (raw)
In-Reply-To: <DS0PR14MB6191FE636A1287711CE03096850D2@DS0PR14MB6191.namprd14.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1744 bytes --]
Hi Janne,
On Fri, Apr 19, 2024 at 06:44 AM, Janne Kiiskila wrote:
>
>
>
> * SRC_URI = "git://${ COMPANY_GIT_REPO }/path/to/project.git;protocol=https;
> *user=token_name:${TOKEN}"*
> * The https+Token was working fine with Dunfell, now I have ported this
> recipe to kirkstone but it is not working and I get this error
> * fatal: could not read Password for 'https://git@COMPANY_GIT_REPO': No
> such device or address
>
>
>
>
> Finally, something I might be able to contribute with.
>
> * Do not put ever any credentials to any recipes. That’s not the right
> place for them and they will leak.
> * Credentials are a build machine configuration issue. You can use git
> redirects for this purpose.
>
>
> This type of thing is only required for private repositories typically,
> here is an example for a GitHub action
>
>
>
> https://github.com/PelionIoT/actions
>
>
>
> that does it. But, essentially it boils down to configuring git:
>
>
>
>
>
>
>
> git config --global user.name "Your BOT"
>
>
>
> git config --global user.email your@email.com
>
>
>
> git config --global url. https://${{ inputs.github_token }}@github.com/ (
> https://$%7b%7b%20inputs.github_token%20%7d%7d@github.com/ ).insteadOf git@github.com:
>
>
>
>
> git config --global url. https://${{ inputs.github_token }}@github (
> https://$%7b%7b%20inputs.github_token%20%7d%7d@github ).insteadOf https://github
>
>
>
>
> I hope this helps.
>
>
>
>
>
>
>
thanks for your help, I will give it a try.
>
>
>
>
>
>
>
>
>
>
>
> Best Regards,
>
>
>
>
>
>
>
> Janne Kiiskilä
>
>
>
Regards,
Salahaldeen Altous
[-- Attachment #2: Type: text/html, Size: 4210 bytes --]
prev parent reply other threads:[~2024-04-22 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 11:55 Http access token fetching with gitsm fetcher alexzoyv
2023-10-20 13:32 ` [yocto] " Adrian Freihofer
2023-10-20 13:43 ` Yoann CONGAL
2023-10-20 14:32 ` alexzoyv
2024-04-19 13:25 ` [yocto] " Altous, Salahaldeen
2024-04-19 13:44 ` Janne Kiiskila
2024-04-22 6:52 ` Altous, Salahaldeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28950.1713768771510530708@lists.yoctoproject.org \
--to=salahaldeen.altous@leica-camera.com \
--cc=janne.kiiskila@izumanetworks.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).