On Tue, 20 Nov 2018 at 11:03, Axel Lebourhis axel.lebourhis@linaro.org wrote:
Ok good to know. Do you have a job definition example including secrets ?
There are quite a few but you need to be a member of the groups who have the rights to access the secrets to see those test jobs.
On Tue, 20 Nov 2018 at 11:46, Milosz Wasilewski milosz.wasilewski@linaro.org wrote:
On Tue, 20 Nov 2018 at 10:42, Axel Lebourhis axel.lebourhis@linaro.org wrote:
Hi everyone,
Is it possible to handle git authentication in a test job ? I need LAVA to clone a repo that can't be set to public, and obviously it won't work because of the authentication step. So is it possible to specify a password or a token ?
You can use 'secrets' section in the job definition. Docs here: https://master.lavasoftware.org/static/docs/v2/publishing-artifacts.html?hig...
It might be also a good idea to limit access to the job to user or group so the password doesn't leak. It has to be plain text unfortunately.
milosz
Lava-users mailing list Lava-users@lists.lavasoftware.org https://lists.lavasoftware.org/mailman/listinfo/lava-users