Sending Jenkins build failures to Discourse

[dLobatog]

I’m neutral about it, to be honest I think it’s easier to post whenever you notice something’s broken like on:

Nightlies assets are now broken

I’ve opened Bug #23721: Nightlies javascript does not work - Foreman to keep track of this. At this moment, nightlies assets do not work. I have not investigated the cause yet. Any help is appreciated!

@tbrisker

The only way to tell now that something is broken is to dig into Jenkins and know which tasks to look at etc., something that only a small group of people know and do on a regular basis

How does that change with a job automatically posting failures to Discourse?

@tbrisker

Right now, if I see a failure on Jenkins, I don’t know if it’s just a random failure, if someone is already working on it, etc. Having each failure as a post in discourse will allow an easy way of collaborating and reducing duplicate efforts.

That’s a good point, but IMO for the sake of having a better noise/signal ratio, a developer can just post here when something is truly broken. If everything gets posted, because of the nature of our jobs (not stable enough, nor we care about it enough) it will be kind of similar to looking at http://ci.theforeman.org/

@tbrisker

One last point that hasn’t been mentioned is that having past failures recorded will allow us to possibly notice patterns or repeated issues, something which now can only be done if the same person happens to handle the same issue multiple times. The resolutions will also be recorded, so if needed in the future other people will be able to reuse them when possible, instead of having to figure out the solution on their own again.

That’s a good point - but again I think it is similar if whoever finds something truly broken posts about it.