[jbosstools-dev] What about a dedicated list for CI builds results?
Max Rydahl Andersen
max.andersen at redhat.com
Mon Sep 24 08:29:59 EDT 2012
>
> I feel having build results on jbosstools-dev introduce a lot of noise and consume a significant amount of time in filering manually.
Something must have changed - before we only got notifications for when the aggregate or continous build failed.
All components were never meant to be sent to the dev list. Someething changed and we should get that changed back because yes, its insane now.
> Jenkins already sends mails to interested people for a job (those who committed code when build status changed, and those who directly add there mail address in the Jenkins notification plugin configuration).
> So I think havng all those mails adds low added-value compared to default Jenkins mailing. I'm fine with the idea of having some notifications of build results, but I'd rather see them in a less critical media that this jbosstools-dev mailing-list which is a good place for discussions.
> What would you think about setting up a jbosstools-builds mailing list to receive notifications? Or what about a jbosstools-notifications list that would contain commits, CI results, and all other automatic stuff that is useful to monitor project activity and health?
We already have that - its at https://lists.jboss.org/mailman/listinfo/jbosstools-builds
/max
More information about the jbosstools-dev
mailing list