[ci] Provide some mechanism to follow the status of a specific FTR config #131879
Labels
enhancement
New value added to drive a business result
Team:Operations
Team label for Operations Team
When CI was broken up manually into CI Groups you could watch a specific CI Group which you knew included some test that you were working on and when it passed you knew your work was done. We lost the ability to do that when we moved to dynamically allocated FTR Config Groups because configs move around and are all in anonymous
FTR Configs #X/Y
groups so the only option is to wait for CI to finish completely.I have a couple ideas for how we might address this, but I'm open to suggestions:
These "separate groups" would really be group types, which are planned and automatically split up based on the expected execution time of those tests. They would often only include a single config but importantly they would report a unique status item to github and run in a separate job in Buildkite so the status of those interesting configs could be watched by PR authors.
We should be able to do just about all of this logic in the ci-stats API, but will need to update the
kibana-buildkite-library
to upload the right pipeline based on the results.Thoughts?
The text was updated successfully, but these errors were encountered: