Instrument job inclusion in the pipeline logger
What does this MR do and why?
pipeline_size_count
is not giving us the number of initial jobs that get filtered out by rules
and only/except
instructions. With this MR we can observe the amount of possible jobs a pipeline could have and the time it takes to evaluate the rules. In this example we see that the pipeline starts of with 778 jobs, but only 130 are created:
{
"pipeline_seed_build_inclusion_duration_s": {
"count": 778,
"min": 9.000010322779417e-06,
"max": 0.05009500001324341,
"avg": 0.009527260926761604
},
"pipeline_size_count": {
"count": 1,
"min": 130,
"max": 130,
"avg": 130
}
}
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Grzegorz Bizon