Pagure CI currently tracks based on "after-the-fact" states. That is, all the states are geared around end-goal rather than the progression of the job.

This is a bit odd compared to other CI systems, and is somewhat confusing as users expect progression for CI reporting.

The consequence of this model is that one of Pagure CI's supported states is oddly defined:

• BUILDING is defined as FLAG_PENDING, and is colored blue (for active)

Also, the states supported are incomplete. What I would expect to have for states are the following:

• PENDING is defined as FLAG_PENDING and is colored gray (for not yet started)
• BUILDING/RUNNING is defined as FLAG_RUNNING and is colored blue (for active)
• SUCCESS is defined as FLAG_SUCCESS and is colored green (for successful completion)
• FAILURE is defined as FLAG_FAILURE and is colored red (for failed completion)
• ABORTED/CANCELED is defined as FLAG_CANCELED and is colored black (for user-canceled)
• SKIPPED is defined as FLAG_SKIPPED and is colored gray (for not being run)
• SUCCESS_WARN is defined as FLAG_SUCCESS_WARN and is colored orange (for successful completion with allowed failures)

Jenkins does support all of these states, but it's also critical for reporting with other OSS CI systems, like Buildbot, Concourse CI, Drone CI, and would be useful for even more specific ones like the simple Koji CI plugin.

The additional states and the focus on progression allows for a richer understanding of what's going on for CI of a particular PR or commit, especially if multiple integrations are in place (though I'm not sure if Pagure supports that yet).