Enable job priority on Android CI Jobs
Bug #1282150 reported by
Alan Bennett
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro Android Build Tools |
Triaged
|
Undecided
|
Paul Sokolovsky |
Bug Description
Currently all Android builds are using default priority, however, using LAVA JSON fields, it's possible to submit jobs in LOW, MEDIUM, and HIGH to make sure the release builds get a higher priority.
Changed in linaro-android-build-tools: | |
assignee: | nobody → Paul Sokolovsky (pfalcon) |
Changed in linaro-android-build-tools: | |
status: | New → Triaged |
To post a comment you must log in.
by submitting the release jobs with higher priority, it can make the release jobs run before daily build jobs,
but still have a problem, hope we can consider it together this time.
wrongly submitted release jobs need to be cancelled manually.
like today, we trigger the release#1 build, but we found it use the wrong manifest after the jobs submitted to LAVA.
after we created the release#3 build, its jobs are queued after the jobs of release#1 build since they will have the same HIGH priority.