Add a /debug command to see what the bots know about a particular issue/PR

tumido commented 3 years ago

Is your feature request related to a problem? Please describe. Time to time I'm setting up the CI process using the Thoth bots for analytics repos. While doing so, I sometimes run into issues which results in a build failure/task not being triggered properly or failing unnoticed etc. Sometimes these errors goes unreported in the release issue and I'm met with a silent treatment from the bots. It's hard to debug it that way and I always have to bother @harshad16 who must be really annoyed by my requests by now.

Describe the solution you'd like I prefer to get my hands dirty so if the issue is obvious and easily fixable I would like to do that on my own without putting more work on @harshad16's plate. It would be nice if we can have a chat-ops command, like /debug or something, which would force sesheta to respond with a list of what it knows about that particular issue/PR:

What tekton pipelines were triggered - with links to the job runs, because it's hard/slow to determine which namespace/thoth runtime is actually the prod now (when there were multiple thoth0*.lab.upshift deployments) and then which of the pipeline run actually is triggered from "my" repo (since they are all named the same, you have to open them all)
Current CI configuration it can parse out of that particular repo
If the proper GitHub apps are set up on the repo, etc.

Describe alternatives you've considered Bother the Thoth team every time:

I use python3.8 Pipfile and try to build it via a python3.6 pipeline
I'm not the maintainer in the CI config (this is being reported by now already)
I'm using the wrong base image for the build
Sesheta is not privileged enough to write to the repo
Having typos in the config

Additional context https://github.com/thoth-station/kebechet/issues/629, https://github.com/aicoe-aiops/mailing-list-analysis-toolkit/issues/18

Issues which resulted in dead silence from the bots and we had hard time debugging it: https://github.com/aicoe-aiops/mailing-list-analysis-toolkit/issues/16 https://github.com/aicoe-aiops/mailing-list-analysis-toolkit/issues/15 https://github.com/aicoe-aiops/categorical-encoding/issues/15 https://github.com/aicoe-aiops/categorical-encoding/issues/16 https://github.com/aicoe-aiops/categorical-encoding/issues/17 https://github.com/aicoe-aiops/categorical-encoding/issues/19 https://github.com/AICoE/s2i-custom-notebook/issues/19

goern commented 3 years ago

/kind feature /priority important-longterm /label hacktoberfest

sesheta commented 3 years ago

@goern: The label(s) /label hacktoberfest cannot be applied. These labels are supported: tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, deployment_name/ocp-test, deployment_name/ocp-stage, deployment_name/moc, thoth/group-programming, thoth/potential-observation, sig/documentation, sig/cyborgs, sig/investigator, sig/indicators, sig/knowledge-graph, sig/solvers, sig/slo, sig/advisor, sig/build, sig/devops

In response to [this](https://github.com/AICoE/aicoe-ci/issues/89#issuecomment-764499636): >/kind feature >/priority important-longterm >/label hacktoberfest Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

goern commented 3 years ago

@tumido is this still required/valid?

tumido commented 3 years ago

I'd still "want" to have that option to be notified at what stage my job is, yes.

sesheta commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

harshad16 commented 3 years ago

/remove-lifecycle stale

sesheta commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

sesheta commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

harshad16 commented 2 years ago

/lifecycle frozen

AICoE / aicoe-ci

Add a /debug command to see what the bots know about a particular issue/PR #89