Description of problem:
Now, 'clang-format' job runs as part of smoke! As it is a mandatory, and as it is a new change, there is high chance of smoke getting negative vote for this job compared to others. It makes sense to run it first, and then only run other jobs. Otherwise, we will be spending too many resources even when we 'technically know' the vote is -1.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Send a patch with known format change issues
2. Trigger regression with marking Verified as +1.
3. See that all smoke job, and regression job still starts and completes
only if clang-format passes, others should be allowed.
This going to take some time to tweak and get right. I'm going to tackle this in sprint 5.