[
https://issues.apache.org/jira/browse/YETUS-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16562056#comment-16562056
]
Allen Wittenauer edited comment on YETUS-647 at 7/30/18 4:01 PM:
-----------------------------------------------------------------
FWIW, it looks like under Jenkins the ssh credentials are never exposed to the
job. That's both good (security!) and bad (our use case). So went the 'ignore
the error' route.
-00:
* if the git repository is either git:// or user@repo, then make the assumption
that pull reset FETCH_HEAD will fail and continue onward
* fix a bunch of shellcheck errors in that code while i'm there
was (Author: aw):
-00:
* if the git repository is either git:// or user@repo, then make the assumption
that pull reset FETCH_HEAD will fail and continue onward
* fix a bunch of shellcheck errors in that code while i'm there
> ssh-based git repos do not work correctly under docker
> ------------------------------------------------------
>
> Key: YETUS-647
> URL: https://issues.apache.org/jira/browse/YETUS-647
> Project: Yetus
> Issue Type: Bug
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Attachments: YETUS-647.00.patch
>
>
> If the git repo that is being operated on is ssh-based, it is impossible to
> use flags like --reset-repo. We should either:
> * figure out how to get the ssh credentials inside the container
> * do all of the git work before launching docker if an ssh-based repo is
> detected
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
