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
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.

Alan Bennett (akbennett)
Changed in linaro-android-build-tools:
assignee: nobody → Paul Sokolovsky (pfalcon)
Revision history for this message
Yongqin Liu (liuyq0307) wrote :

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.

Revision history for this message
Yongqin Liu (liuyq0307) wrote :

One thing I found that the non CTS test job will get run before other cts jobs, even it submitted later than the cts jobs.

it is similar to this priority solution.

Milo Casagrande (milo)
Changed in linaro-android-build-tools:
status: New → Triaged
Revision history for this message
Chase Qi (chase-qi) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.