-
Notifications
You must be signed in to change notification settings - Fork 47
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
Do not flood the logs with branch-api causes #36
Conversation
We tested this on our instance and it works. Any feedback from your side would be appreciated. |
@fabiodcasilva: Any chance this gets merged? We have this running within our instance for a couple of months now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will leave this with "request changes" until I find out the answer.
<artifactId>branch-api</artifactId> | ||
<version>2.6.0</version> | ||
<optional>true</optional> | ||
</dependency> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this force my jenkins instance to install the branch-api plugin when I don't need it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is marked as optional as stated here: https://www.jenkins.io/doc/developer/plugin-development/optional-dependencies/
So you do not need this dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Since we are using the branch-api plugin together with GitHub our log is flooded with lines like this:
Since this cause is never triggerd by a user, I just want to ignore it.