Closed sinlov closed 5 months ago
In 2.0.0, plugin-git supports ssh cloning. It must be enabled manually. Does this fix the issue? (See https://github.com/woodpecker-ci/plugin-git/pull/75)
@qwerty287 version 2.x
with local backend mode, support clone via SSH instead of HTTP can change git global config like this
git config --global url."git@git.xxx.com:".insteadOf "https://git.xxx.com/"
so, please close this issure
Clear and concise description of the problem
Currently woodpecker clones the repositories via HTTP, but some git ssh config must use custom config.
git config
as ssh_configdifferent ssh clone config
at different ssh clone piplineSuggested solution
setting
woodpecker-agent
argWOODPECKER_CUSTOM_SSH_GROUP_ROOT
config
custom_ssh_group
setting byname
towoodpecker-agent
path$HOME/.ssh/
for git ssh to useAlternative
config
at woodpecker agent asWOODPECKER_CUSTOM_SSH_GROUP_ROOT
when$HOME/.ssh/config
after workspace init. this path callcustom_ssh_group_root
.WOODPECKER_CUSTOM_SSH_GROUP_ROOT
can set from volume or local pathcustom_ssh_group_root
file map ascustom_ssh_group
setting byname
towoodpecker-agent
path$HOME/.ssh/
for git ssh to useconfig
file format as ssh_configknown_hosts
file is optionaldefault
folder is default ssh config, this is necessary,so less file map aspipeline-syntax
atclone
can config bysettings.custom_ssh_group.dryrun_host
asstring
can set ssh testhost
WOODPECKER_CUSTOM_SSH_GROUP_ROOT
andname
setexec
asssh -vT <dryrun_host>
for check ssh configAdditional context
No response
Validations
next
version already [https://woodpecker-ci.org/faq#which-version-of-woodpecker-should-i-use]