docs/devel: add CI monitoring information for developers#1221
Conversation
Update development.md with useful information about monitoring dashboards to investigate CI build issues.
|
This issue is currently awaiting triage. If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the The DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Hi @mtulio. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/ok-to-test |
|
/lgtm |
|
/lgtm |
|
@jcpowermac: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elmiko The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Update docs/development.md with useful information about monitoring dashboards to investigate CI build issues.
With this change, developers will have more information about failures in their PRs and CI test infrastructure, allowing them to investigate and distinguish between CI infrastructure issues and code-related failures.
The main motivation is to:
Which issue(s) this PR fixes:
Fixes #
Related to:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: