Add repository name to the scheduled mi workflows
Closed this issue · 12 comments
Is your feature request related to a problem? Please describe.
Hello! Currently, the mi workflows are scheduled with names as follows:
mi-analysis-mi-210715120822-ab98e5f26d2b4148 Pending 2h 0s 0
mi-analysis-mi-210715120822-b2b1cee430cca8e7 Pending 2h 0s 0
mi-analysis-mi-210715120821-7feec52461ef063d Pending 2h 0s 0
mi-analysis-mi-210715120821-94fdbb46715585e7 Pending 2h 0s 0
mi-analysis-mi-210715120821-9aacbfe9bc0e92bc Pending 2h 0s 0
mi-analysis-mi-210715120821-bc902f486165a4dd Pending 2h 0s 0
mi-analysis-mi-210715120821-cd7c7ecadd842c83 Pending 2h 0s 0
Which is fine, but is really not that informative. Better naming convention would contain repository name (and maybe appended entities that are being inspected?! but that's another step).
Describe the solution you'd like
instead of mi-analysis-mi-{ID} have something like
mi-analysis-{repo_name}-{ID}
or even
mi-analysis-{repo_name}-{entities}-{ID}
where entities is substitued by { <entity_name> }⁺ . { _ . <entity_name> }* as in ebnf-styled grammar
Use case
If workflow fails, maintainer does not have to look into logs what repository failed specifically
/priority important-soon
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
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@sesheta: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./close
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/test-infra repository.
/reopen
/remove-lifecycle rotten
@xtuchyna: Reopened this issue.
In response to this:
/reopen
/remove-lifecycle rotten
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/test-infra repository.
/priority-important soon
@xtuchyna: The label(s) priority/soon cannot be applied, because the repository doesn't have them.
In response to this:
/priority-important soon
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/test-infra repository.
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
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
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@sesheta: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten./close
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/test-infra repository.