TrevorGibson-SR
commented
1 year ago Update for Issue 2
I was able to solve the issue of cloning a single non-GitHub private repo in the Docker container by adding that repository's server to the known_hosts file. I believe this is what was causing the build process to hang as it was waiting for user input to add the server to the list of known hosts.
This was fixed by issuing the following command immediately after the ssh-agent action in my GitHub workflow:
ssh-keyscan -H bitbucket.org >> ~/.ssh/known_hosts
After investigating the contents of the known_hosts file, it appears that github.com had already been added (either by the workflow managing agent, or by the ssh-agent action), which is why there weren't any issues cloning GitHub repositories.
This solution should work for repositories hosted on any non-GitHub servers... just replace bitbucket.org with the repo server's domain.
AndyZe
mathias-luedtke
Hi all,
I've been trying to get a GitHub Actions CI build to work with cloning more than one private repository, but have run into multiple issues and can't seem to resolve them.
Overview
The current Action I have set up works fine specifically when only 1 private GitHub repository is listed in our
.reposfile. It breaks when either a second private GitHub repo is listed (issue 1), or any private BitBucket repositories are listed (issue 2).Some additional information:
vcs import) works fine, regardless of the source of those repos (GitHub or BitBucket)Here is a snippet of the .yml action showing the steps being run (placeholders in place of actual repo URLs):
KEY1,KEY2, andKEY3are action secrets defined in the main repository, and contain the private keys for the corresponding private repositories we want to clone.Issue 1: Action fails when cloning a second private GitHub repository
Prior to running the industrial CI step, I have an
ssh-agentstep to load the SSH keys and allow for cloning private repositories. The output from this step indicates that the keys are being scanned and added correctly. Additionally, I have added the repository links for the GitHub repos as comments for the keys to use the deploy key mapping feature of thessh-agentaction (actual keys/hashes redacted for security):However, during the cloning process in the industrial CI step, only the repository for the first key listed is successfully cloned. If I switch the key order in the .yml action file, the successfully clone repository changes as well. Failure output:
Issue 2: Action hangs when cloning any number of private BitBucket repositories
Similar to above, the
ssh-agentstep successfully loads the SSH keys prior to running the industrial CI step. When a private BitBucket repo is listed in the.repos file, the action hangs during thecolcon_setupportion and must be manually cancelled. It always hangs at the same point, prior to even attempting to clone the repos in the.reposfile. Output log:Summary
Any help with either of these issues would be greatly appreciated. Ideally I would like to use the BitBucket private repo as it works better with the larger project architecture. However, cloning multiple private GitHub repositories is also a must for another project, so resolving that one alone will be helpful as well.
Thanks in advance