Project

Profile

Help

Task #2617

Reevaluate Jenkins build notifications in IRC

Added by semyers 10 months ago. Updated 9 months ago.

Status:
NEW
Priority:
Low
Assignee:
-
Category:
-
Sprint/Milestone:
-
% Done:

0%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No

Description

With the migration of our jenkins master from el6 to el7, the jenkins IRC Notifications plugin is not longer available. This isn't really a bad thing, since the IRC plugin has several drawbacks:

  • The plugin is easy to set up, but the value it provides is questionable since it only reports PASSED/UNSTABLE/FAILED
  • The job notification template is not customizeable, and neither are other silly notifications like "Yippee! Build Fixed!".
  • Related to the previous bullet, job notifications include rh-only jenkins urls that are useless to non-rh folks in #pulp-dev

So, rather than invest a ton of time getting the IRC notification plugin working in the new environment, and possibly having to justify our need for a plugin that spews internal URLs into a public IRC channel, I propose we find another way.

History

#1 Updated by semyers 10 months ago

So this task is two major pieces, I think.

The first piece is to reevaluate whether or not we really want/need jenkins build notifications in IRC. My personal opinion is that these notifications do not give a useful representation of the actual health of our jenkins jobs, so it would be worth it to ask what information from jenkins would actually be useful when presented to the team in this medium.

The second piece, assuming the first part bears fruit and we come up with specific information that we want to see in #pulp-dev, involves figuring out how to get that information. Jenkins has several ways to get at its job status info, including (but not limited to):

  • subscribing to the CI event bus, to which jenkins posts events
  • subscribing to the ZMQ endpoint provided by our jenkins, to which jenkins similarly post events (this is part of how nodepool hooks into jenkins)
  • use the jenkins API, for which python bindings exist
  • probably other things I'm forgetting

Any combination of these could be used fairly simply, in my opinion, to put together a little plugin for pulpbot that gets us the information we actually want from jenkins, assuming we identify that some information is actually wanted.

#2 Updated by bmbouter 10 months ago

In regards to the "first piece" of determining their value... I was one of the early requestors to enable the notifications via IRC. After having them working for a long time, I don't derive much benefit from them. They also lower the information density with each updates, so I +1 closing this issue to track bringing them back.

#3 Updated by jortel@redhat.com 9 months ago

bmbouter wrote:

In regards to the "first piece" of determining their value... I was one of the early requestors to enable the notifications via IRC. After having them working for a long time, I don't derive much benefit from them. They also lower the information density with each updates, so I +1 closing this issue to track bringing them back.

+1

#4 Updated by bmbouter 9 months ago

Do we want to close this issue? It could be closed as WONTFIX I think.

Please register to edit this issue

Also available in: Atom PDF