Hi,
I want clone a gitlab repo with id and token during job execution. To hide the token I am passing the value in my job. How can I export the value of GIT_TOKEN in environment file of LAVA? So that whenever job is executed it will read the value from its environment file. I tried to use export and tried to add "GIT_TOKEN=abcd" in env.yaml file. But I guess its not correct format. I couldn't find what kind of values we can add in env.yaml in documents. I also added GIT_TOKEN value in /etc/profile of the LAVA server still the job didn't pick it. Could you please suggest how can we clone the repo in LAVA job without exposing its password. Also I understand that ssh key of root will work but I want to avoid using ssh key of root. Kindly suggest
- test:
timeout:
minutes: 15
definitions:
- repository: https://gitid:$GIT_TOKEN@gitlab.com/lava-tests.git
from: git
path: tests/cisscan/cis.yaml
branch: pipeline
name: cis-benchmark
Hi all,
I run into some unexpected behavior when it comes to LAVA job IDs
reported by the "lavacli jobs sumit" command for multi node tests.
What I get is a list of newline separated job IDs like:
lavacli jobs submit <my-job-description>
132.0
132.1
To my understanding this tries to express that 132.1 is a sub job of
132. OK, but this is a problem if I now try to download the junit
report for the second job (=132.1).
It seems 132.1 is not a valid job ID (API wise), it has to be
translated to 133 to work properly.
This is still doable, but I'm unsure if I can relay on 133 really being
the 132.1 job in case there are several job submissions at the same
time.
Is that a bug of lavacli? What is the reasoning for returning a sub job
ID which seems to be invisible to the rest of the LAVA infrastructure /
API?
I'm currently running lavacli 1.2-1, as shipped by Debian 12.
Any input welcome...
Best regards,
Florian
