We're updating the issue view to help you get more done. 

Standardize build statuses for all our Jenkins jobs

Description

Currently, our Jenkins jobs don't make enough use of the "Unstable" build status. Only a few of the jobs report failed tests as "Unstable", all others report them as "Failed".

In order to differentiate between failed builds (because of the infrastructure) and builds that failed due to tests catching regression, we should unify our builds to do the following:

  • If the build/tests passed, report the build as successful (green)

  • If the build passed, but the tests or quality gate, in general, didn't pass, report the build as unstable (yellow)

  • If the build didn't manage to complete for any reason, report the build as failed (red)

Status

Assignee

Paweł Cieszko

Reporter

Sebastian Brudziński

Labels

None

Story Points

3

Time tracking

32h

Components

Sprint

None

Fix versions

Priority

Major