Skip to content
This repository has been archived by the owner on Jun 9, 2023. It is now read-only.

[5pt] Introduce a verbose mode for job summaries #59

Open
3 tasks
mayaCostantini opened this issue Jun 22, 2022 · 6 comments
Open
3 tasks

[5pt] Introduce a verbose mode for job summaries #59

mayaCostantini opened this issue Jun 22, 2022 · 6 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@mayaCostantini
Copy link
Contributor

mayaCostantini commented Jun 22, 2022

Is your feature request related to a problem? Please describe.

As a user of the Thoth action, I would like the option to get a more complete job summary containing information about dependencies from the advise report.

Describe the solution you'd like

  • Establish a list of advise report parts which would be the most useful for users to see in a job summary vs. in the Search UI
  • Parse the advise report and add those parts to the summary with correct formatting
  • Nice to have: add more information about the CVE detected (severity, attack vectors, fixable...) directly available to the users.

This issue could eventually be completed after thoth-station/core#417 to keep the same advise results clustering logic in all Thoth integrations.

Describe alternatives you've considered

Have the advise report in the workflow logs only or leave all information in the Search UI.

@mayaCostantini mayaCostantini added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 22, 2022
@mayaCostantini
Copy link
Contributor Author

/sig stack-guidance
/priority important-soon

@sesheta sesheta added sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 22, 2022
@mayaCostantini
Copy link
Contributor Author

depends on thoth-station/adviser#57

@mayaCostantini
Copy link
Contributor Author

/good-first-issue

@sesheta
Copy link
Member

sesheta commented Jun 27, 2022

@mayaCostantini:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.

@sesheta sesheta added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jun 27, 2022
@sesheta
Copy link
Member

sesheta commented Sep 25, 2022

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 sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2022
@codificat codificat moved this to 📋 Backlog in Planning Board Sep 26, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants