Early Run Flag

Registered by Zygmunt Krynicki

Looking at bug https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1329687 made me realize that we should differentiate typical test run from the early test run that we currently utilize in checkbox-ng and checkbox-gui (but not in plainbox, hence it being missing) that is required to obtain the full set of tests. In other words, when running local jobs (and their dependencies) early on we should be careful not to run jobs that typically run later, and might for example, suspend the machine.

Since local jobs are just a special case of a mechanism that generates jobs (job templates are a replacement mechanism under development) we should make sure that any safety feature can work effectively both now and later on.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Zygmunt Krynicki
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Sylvain Pineau

Related branches

Sprints

Whiteboard

(?)

Work Items

Work items:
Recognize a new flag (on job definition unit) called 'early-run-job'. The flag should be documented in planinbox docs: TODO
Within manage.py validate we should validate whitelists (test plans) (this is under development and will land soon): INPROGRESS
Test plan validation should (for each provider test plan) perform a early-run selection and see if all of the selected jobs have the 'early-run-job' flag. Any unaccounted job should fail the validation. This validation should be DISABLED by default: TODO
Work with OEM-QA and internally to ensure that all providers are safe. Flag each job that needs to run as a part of the early sequence with the new flag.: TODO
Enable the validation by default.: TODO
During normal execution we should reject such providers as invalid and utilize the same error handling code as today: TODO

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.