https://pulp.plan.io/https://pulp.plan.io/favicon.ico2017-03-01T16:36:06ZPulpPulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=183032017-03-01T16:36:06Zsemyerssean.myers@redhat.com
<ul></ul><p>So this task is two major pieces, I think.</p>
<p>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.</p>
<p>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):</p>
<ul>
<li>subscribing to the CI event bus, to which jenkins posts events</li>
<li>subscribing to the ZMQ endpoint provided by our jenkins, to which jenkins similarly post events (this is part of how nodepool hooks into jenkins)</li>
<li>use the jenkins API, for which python bindings exist</li>
<li>probably other things I'm forgetting</li>
</ul>
<p>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.</p> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=183042017-03-01T17:55:15Zbmbouterbmbouter@redhat.com
<ul></ul><p>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.</p> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=184992017-03-13T16:17:39Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>bmbouter wrote:</p>
<blockquote>
<p>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.</p>
</blockquote>
<p>+1</p> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=186292017-03-21T13:10:36Zbmbouterbmbouter@redhat.com
<ul></ul><p>Do we want to close this issue? It could be closed as WONTFIX I think.</p> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=370612019-04-12T19:43:49Zbmbouterbmbouter@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>CLOSED - WONTFIX</i></li></ul> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=371162019-04-12T19:48:16Zbmbouterbmbouter@redhat.com
<ul></ul><p>Pulp 2 is approaching maintenance mode, and this Pulp 2 ticket is not being actively worked on. As such, it is being closed as WONTFIX. Pulp 2 is still accepting contributions though, so if you want to contribute a fix for this ticket, please reopen or comment on it. If you don't have permissions to reopen this ticket, or you want to discuss an issue, please reach out via the <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" class="external">developer mailing list</a>.</p> Pulp - Task #2617: Reevaluate Jenkins build notifications in IRChttps://pulp.plan.io/issues/2617?journal_id=383972019-04-15T20:20:25Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>