Package: lava-test-plans
lava-test-plansThe lava-test-plans project makes it easier to generate LAVA job definition files.
It generates the LAVA job definition file from a set of templates.InstallationInstall lava-test-plans from pip:lava-test-plans -horvia podman/docker:docker run -i -t lavasoftware/lava-test-plans /bin/bashlavasoftware/lava-test-plans:latest points to the latest released version.
lavasoftware/lava-test-plans:master points to the latest development.If the above commands succeed, you can run to check that the program starts correctlylava-test-plans -hDevelopingTo install the latest development version:git clone https://github.com/Linaro/lava-test-plans.git
cd ./lava-test-plans

pip3 install flit
flit install --symlinkorYou need to do if you have docker installed:docker run --volume $HOME/path/to/lava-test-plans:/xyz -i -t lavasoftware/lava-test-plans /bin/bash
cd /xyzlavasoftware/lava-test-plans:latest points to the latest released version.
lavasoftware/lava-test-plans:master points to the latest development.There will be a directory with /lava-test-plans from either a "released"
version or directly from master.If the above commands succeed, you can run to check that the program starts correctlypython3 -m lava_test_plans -hExternal variablesExternal variables are set in thevariables.inifile. Each line in this file
is in the formkey=valueLines starting with#are omited. Variables can also be set using--overwrite-variablesparameter. List of used variables:PROJECT_NAME: used as the first part in the test job name. Can be set to
differentiate LAVA test jobs between different teams/projectsBUILD_NUMBER: used as last part in the test job name.KERNEL_BRANCH: used in test job nameOS_INFO: used in test job nameLAVA_JOB_PRIORITY: priority of the LAVA job, used by LAVA schedulerLAVA_JOB_VISIBILITY: defaults topublic. This block can be used to restrict job visibility to user or group.LAVA_JOB_VISIBILITY_GROUPS: variable should contain groups required by job. Formtatting is important and this variable should be
formatted comma separated list. Example: group1, group2. In case of using just one group, end string with comma. Example:
group1,AUTO_LOGIN_: default *PROMPT='login:', *USERNAME='root' and *PASSWORD=''.BOOT_LABEL: default BOOT_LABEL='boot'.TAGS: variable should contain tags required by job. Formtatting is important and this variable should be
formatted comma separated list. Example: tag1, tag2. In case of using just one tag, end string with comma. Example:
tag1,UBOOT_VERSION_STRING: string that is matched in the u-boot shell from output of commandversionOVERLAY_MODULES_*: overlays modules into the rootfs.TEST_DEFINITIONS_REPOSITORY: points to the test repository to use, default:https://github.com/Linaro/test-definitions.gitVariables can also be stored in YAML file. Usual YAML syntax applies.TimeoutsOverall job timeout is a sum of action timeouts. There are 6 components:deploy_timeoutboot_timeoutinstall_fastboot_timeoutfastboot_deploy_timeouttarget_deploy_timeoutTARGET_BOOT_TIMEOUTtest_timeoutWhen LXC is not in use alllxc_timeouts are set to 0.test_timeoutis defined for each test template.target_timeouts can be set separately for each device.CI for docker multiarch buildslava-test-plans gets mirrored to gitlabhttps://gitlab.com/Linaro/lava-test-plansto build multiarch docker containers
and publish them tohttps://hub.docker.com/r/lavasoftware/lava-test-plans, that
is why there is a .gitlab-ci.yml in this repository.RepositoryPull requests are welcome tohttps://github.com/linaro/lava-test-plans.