Hi all,
thank you for your suggestions! I googled a bit more and found this guide:
https://docs.gitlab.com/ce/ci/ssh_keys/README.html#ssh-keys-when-using-the-docker-executor
That is exactly what I was looking for! In this way I can avoid storing
keys in the containers and feeding it only when th
Hej,
I use for this secret variables and store the access tokens or ssh keys
in in one of this. A script running inside of the docker container uses
sed magic for replacing string, when ever the direct usage of the secret
variables is not possible. The ssh key is then written in a first step
with
That's more of a Gitlab than Yocto question. I am doing this all the time
with my GL server on AWS. You need to add deploy a key to the repo you want
to access and then push the key to your Docker instance from gitlab-ci.yaml
from the repo that you are using with GL CI.
:rjs
On Mon, Jun 17, 2019,
