Need a way to send multiple LAVA jobs from a single CI job
Bug #1090416 reported by
Milo Casagrande
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Fix Released
|
Medium
|
Milo Casagrande |
Bug Description
The code to send a LAVA job fron the continous integration service is able to send only one job, based on the 'board_type' env variable declared in the config.
We need a generic way to define multiple board types in a single CI job, and submit different LAVA jobs based on that.
Use case is to test the same artifacts (an hardware-pack usually) on multiple boards.
Related branches
lp:~milo/linaro-ci/bug1090416
- James Tunnicliffe (community): Approve
- Deepti B. Kalakeri (community): Needs Fixing
-
Diff: 344 lines (+141/-122)5 files modifiedget_latest_ci_hwpack (+122/-111)
jenkins_common_lib (+1/-1)
jenkins_kernel_build_inst (+9/-4)
jenkins_lava_job_submissions (+6/-3)
jenkins_packaged_kernel_build_inst (+3/-3)
Changed in linaro-ci: | |
assignee: | nobody → Milo Casagrande (milo) |
status: | New → In Progress |
importance: | Undecided → Medium |
Changed in linaro-ci: | |
status: | In Progress → Fix Committed |
milestone: | none → 2013.01 |
Changed in linaro-ci: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The code used in linaro-ci to send LAVA jobs is in: lava_job_ submission (bash) ci_hwpack (python)
- jenkins_
- get_latest_
Approaches I can see:
- Rewrite the first in Python and clean-up a little bit the second, so we can also write tests for them
- Just cycle through the defined boards in a env variable in the bash script, passing the board name as an argumento to the python script, the python script needs to be refactored a little bit anyway
The part that really sends the job is the bash script.