Learn more about these different git repos.
Other Git URLs
When an user name is needed for the git checkout to build the srpm package, it will lost at the builder. Sample: On the client: koji build --scratch <tagret> 'git+https://<username>@<git server>/<path to repo>#<tag>' But the check out on the builder(checkout.log) fails with: fatal: could not read Username for 'https://<git server>': No such device or address It looks like the user name was not forward from the client to the hub/builder.
koji build --scratch <tagret> 'git+https://<username>@<git server>/<path to repo>#<tag>'
fatal: could not read Username for 'https://<git server>': No such device or address
User is allowed in git+ssh scheme. Isn't that git server allowing also that option (as a workaround)? We can add support for that anyway.
Metadata Update from @tkopecek: - Custom field Size adjusted to None
Metadata Update from @tkopecek: - Issue set to the milestone: 1.26
Or I am on the total wrong way to set the credentials for the https git access?
It depends - I don't know that repo :-) git+https + user is completely valid usage for git repos. Anyway, vast majoristy of repos we're tackling with has anonymous access via https, so we just hadn't hit git+https+user combination.
Setting credentials is not that easy - we can't pass password from user to builder (it would be visible in too many places), so only administrator can put credentials on every builder (PR #1640). So, mostly only repos accessible without authentication makes sense for end-user. So, we're stripping username intentionally there.
In that case it is an git repo accessible via git+https with user name + password. But the password is not an real password. It is only an token with read only permissions. It works like git hub when using git tokens.
Ok, then we have to add support for that. Added to next release - should be simple change.
Thanks :thumbsup:
Metadata Update from @tkopecek: - Issue tagged with: feature
Metadata Update from @tkopecek: - Issue set to the milestone: 1.27 (was: 1.26)
PR 3067
Metadata Update from @jcupova: - Issue tagged with: testing-ready
Metadata Update from @mfilip: - Issue tagged with: testing-done
Commit a4f16fe fixes this issue
Commit 6426ddc fixes this issue
Login to comment on this ticket.