Optimized tests and build launch in order to save system resources and stabilize tests
- Launch tests, tests reports upload and email sending of test report only when in MR and when MR isn't in state Draft or nightly (to ensure that long pipelines will be only launched once for a merge. tags won't trigger builds/tests)
- Launch 30 tests suites at once by specifying it directly in linux test job
- Draft status doesn't trigger any pipeline
Edited by Peio Rigaux