[vtk-developers] Dashboard

[Marcus D. Hanwell]

On Thu, Mar 21, 2013 at 11:39 AM, David Gobbi <david.gobbi at gmail.com> wrote:
> On Thu, Mar 21, 2013 at 9:32 AM, Marcus D. Hanwell
> <marcus.hanwell at kitware.com> wrote:
>> On Thu, Mar 21, 2013 at 11:22 AM, David E DeMarle
>> <dave.demarle at kitware.com> wrote:
>>>
>>> Having a 100% clean nightly is not going to happen, probably even with a
>>> next/master workflow like ParaView has (although that would bring us closer
>>> to that "guarantee").
>>>
>> I second the "that's what nightlies are for" sentiment - they provide
>> wider coverage. I can take a look at increasing the warning levels on
>> the CDash at Home machines, Linux will be fairly easy and tips are
>> welcome for the other platforms.
>
> Yup, nightlies will break from time to time.  That's a given.  I think
> a lesson is being missed here, though.  If you commit something that
> breaks the dashboard, send a polite email to the list:
>
> "Oops.  I think I broke something on the dashboard.  I'll investigate".
>
> That alone will be a big help to other developers.
>
Agreed, or someone will come and chase you down. I attempted to update
the commit policy to reflect this, but perhaps a word about mailing
the list to confirm you saw it would be good.

http://vtk.org/Wiki/VTK/Commit_Guidelines

Marcus