Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to configure health options of the warnings-ng plugin? #57

Open
rhaschke opened this issue Sep 11, 2021 · 3 comments
Open

How to configure health options of the warnings-ng plugin? #57

rhaschke opened this issue Sep 11, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@rhaschke
Copy link
Contributor

The warnings-ng plugin provides several options to monitor the health status of a job. However, it is unclear how to configure those in recipes. Particularly, I would like to configure the following settings:

  • healthy/text()
  • unhealthy/text()
  • minimumSeverity/name/text()
  • qualityGates (the only way to yield a FAILED or UNSTABLE on too many issues)
@rhaschke rhaschke added the enhancement New feature or request label Sep 11, 2021
@rhaschke
Copy link
Contributor Author

rhaschke commented Nov 3, 2021

@scymtym, did you made some progress on this already?

scymtym added a commit that referenced this issue Nov 3, 2021
@scymtym
Copy link
Member

scymtym commented Nov 3, 2021

I made a branch which looks like it could work. You can try the binary from https://github.com/RDTK/generator/actions/runs/1416420320 (the other pipelines seem to be broken due to either end-of-life of the runner configuration or the recent libSSL woes).

build-generator version -c 1 has a brief description.

rhaschke pushed a commit to rhaschke/generator that referenced this issue Mar 1, 2022
@rhaschke
Copy link
Contributor Author

rhaschke commented Mar 2, 2022

Thanks for preparing this branch, @scymtym. Sorry, that I only found time to test this now. Here are my observations:

  • Defining the healthy-threshold, unhealthy-threshold, and health-minimum-severity works as expected.
  • I couldn't figure out, how to define a quality gate. The doc doesn't mention this.
  • One quality gate is created by default, although the list of gates should be empty I think.
  • This created quality gate has a threshold of zero, which is forbidden.
  • The cmake warnings parser isn't registered anymore. Maybe, because the name changed from Cmake to CMake?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants