This repository was archived by the owner on Jan 23, 2020. It is now read-only.
Lower event priority for non-failure events#86
Merged
Conversation
sjenriquez
force-pushed
the
scott/priority-alert-types
branch
from
May 25, 2017 16:03
f2f03a2 to
c80aa46
Compare
sjenriquez
force-pushed
the
scott/priority-alert-types
branch
2 times, most recently
from
May 25, 2017 17:52
8c1ced5 to
36dbdac
Compare
sjenriquez
force-pushed
the
scott/priority-alert-types
branch
from
May 26, 2017 21:16
36dbdac to
e7c8555
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR sets all non-failure Jenkins events to
lowpriority.Lower non-failure priority levels was a customer request to reduce noise in the Event Stream.