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

Verbosity of the Library Log entries in Jenkins console log. #36

Open
leonvzGit opened this issue Jul 9, 2021 · 0 comments
Open

Verbosity of the Library Log entries in Jenkins console log. #36

leonvzGit opened this issue Jul 9, 2021 · 0 comments
Labels
type:feature New feature or request that provides value to the stakeholders/end-users

Comments

@leonvzGit
Copy link

leonvzGit commented Jul 9, 2021

Hi,
We have multiple services in a keptn project and we find that there is a lot of log output in the Jenkins console log coming from the Jenkins Keptn Library. The root cause of this is some of the API calls to keptn that are using the Jenkins HttpRequest plugin are verbose so the response of the request is shown in the log.
eg:
The Get project and get stage functions in the library. Shows the result in the console:
/api/configuration-service/v1/project/my-project : shows the json Response from get project in the log and
/api/configuration-service/v1/project/v1-application-market/stage/mystage : shows the Json response in the log.
This results in 100s of lines in the log in our case.
Please add the property quiet: true (or make it optional) to the httpRequest call, so I can control the verbosity of the output in the log.https://www.jenkins.io/doc/pipeline/steps/http_request/
Thanks,
Leon

@christian-kreuzberger-dtx christian-kreuzberger-dtx added the type:feature New feature or request that provides value to the stakeholders/end-users label Oct 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or request that provides value to the stakeholders/end-users
Projects
None yet
Development

No branches or pull requests

2 participants