Add glossary entries for pipeline breakdown metrics #29534
Conversation
|
Created DOCS-11021 to get our CI expert's eyes on this 🙂 |
There was a problem hiding this comment.
Approved with a few small edit suggestions. Also, it's a bit atypical for the glossary to include granular details like tag names; most entries link to docs for more details. But there isn't currently a good home for this info in the docs, so makes sense to include in the glossary for now. Thanks!
content/en/glossary/terms/pipeline_breakdown_uncategorized_time.md
Outdated
Show resolved
Hide resolved
✅ Documentation Team ReviewThe documentation team has approved this pull request. Thank you for your contribution! |
Co-authored-by: Joe Peeples <joe.peeples@datadoghq.com>
| --- | ||
| Total amount of time spent by CI jobs on the critical path executing tasks. | ||
|
|
||
| The sum of all the breakdown metrics is equal to the pipeline duration (`@duration`). |
There was a problem hiding this comment.
I'm not convinced about this. I had to read it a few times to realise it was referring to the rest of pipeline breakdown X metrics that we have in the glossary. I'd list them here to be clear on what we mean.
There was a problem hiding this comment.
I added the pipeline word before breakdown so it is a bit clearer but I think this will be more intutuive if we look it from the UI were all the entries will be consecutive
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-mergequeue
bot
deleted the
rodrigo.roca/add-glossary-entry-pipeline-breakdown-tags
branch
dd-devflow
bot
added
mergequeue-status: done
and removed
mergequeue-status: in_progress
labels
What does this PR do? What is the motivation?
We are adding 4 new metrics to the pipeline level for all CI providers in CI Visibility.
Merge instructions
Merge readiness:
For Datadog employees:
Merge queue is enabled in this repo. Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass in CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
To have your PR automatically merged after it receives the required reviews, add the following PR comment:
Additional notes