Indicate smoke+bvt status for public nightly builds

[Dmitry Borodaenko]

Nightly builds published at https://fuel-jenkins.mirantis.com/view/ISO/job/publish_fuel_community_iso/ should be updated with green/red status depending on whether smoke and centos/ubuntu bvt tests have passed for the same ISO in our internal jenkins. Status should be green if smoke and both bvt's passed, and red otherwise.

[Mike Scherbakov (mihgen)]

I think we are free for indication, however the idea is that user must be able easily find:
1) nighly build ISO regardless of whether it passes smoke or not, with date of the build and ISO # defined near the link
2) Last ISO which passed BVTs, with date of the build and ISO # defined near the link

Raising this to High. We would like to see this working in 5.1 (where we don't keep Mediums after SCF), and at least 2 weeks before release, so we can get feedback from users.

[Aleksandra Fedorova (bookwar)]

The nightly builds we publish at Fuel CI are different from iso builds we tests internally. I don't think we should mix their statuses.

We had a plan to run additional smoke test on each nightly build on Fuel CI and use it as a status.

Should we run both BVT jobs as well?

[Dmitry Borodaenko (angdraug)]

I think we should. These builds should receive at least as much automated testing as the internal builds, it would be poor form to have less automated testing for builds we publish externally.