(This has been discussed a bit privately, so I thought it was time to make an RFC)
We’ve got ongoing issues with many of the jobs on Jenkins (notably the nightly builds, but others such as plugins too). A proposal has been made to send the build failures to Discourse, both to increase visibility of the failures, and also raise awareness of the CI processes so that others can help out.
- Create a new category (suggestions for name? I’m going with “CI failures” so we can use it for more than just Jenkins if we wish)
- Have Jenkins send build failures to the category via the Discourse API
- The created topics should be tagged with something relating to the job name
- As many people as possible add the whole category (or at least the specific job tags they can help with) to their notifications, so they know about failures
- When a failure occurs, the first person to pick it up replies to the thread stating they’re working on it
- The topic is closed (or perhaps “marked as solved”) once the failure is fixed
Notes / optional extras:
- We need lots of buy-in here. A new category won’t have any subscribers initially so people will need to opt-in to it.
- Mailing-list-mode members will get every single failure - sorry . But more seriously, if that’s an issue, consider more fine-grained configuration in your settings
- Volume of traffic from Jenkins needs to be monitored (we already send 35k emails per month, I don’t want that to rise too much)
- We could look at using the Assigned-To plugin for tracking whose working on topics.
This is worth trying, IMO. I will post a poll shortly, but I hope we can agree that trying things out and iterating from there is better than not changing anything. We should evaluate after a couple of months and see what (if anything) needs tweaking.
- per @tbrisker - category should be positive, such as “Build Status”