VTK/SoftwareQuality/VTKDashboardHackathon1: Difference between revisions
From KitwarePublic
< VTK
Jump to navigationJump to search
(→Define) |
(→Agenda) |
||
| Line 21: | Line 21: | ||
* 15:00 - Group Gerrit Review 2 | * 15:00 - Group Gerrit Review 2 | ||
* 15:45 - Summary reports | * 15:45 - Summary reports | ||
** [http:// | ** [http://review.source.kitware.com/#/q/entity:topic%20status:open+project:VTK,n,z Gerrit topics] | ||
** [ | ** [[VTK/SoftwareQuality/GerritTestFailures|Gerrit builds]] | ||
** [ | ** [[VTK/SoftwareQuality/ContinuousBuildTestFailures|Continuous builds]] | ||
** [[VTK/SoftwareQuality/NightlyExpectedBuildTestFailures|Nightly Expected builds]] | |||
* 16:30 - Action items | * 16:30 - Action items | ||
* 17:00 - Adjourn | * 17:00 - Adjourn | ||
Revision as of 18:08, 22 February 2013
The first VTK Dashboard Hackathon is scheduled for February 27, 2013. The purpose of this hack-a-thon is to drive the number of recurring, failing test defects to 0 on the VTK Nightly Expected dashboard.
Logistics
- Location: Kitware, Clifton Park
- Google Hangout: TBD
- Beer celebration: TBD
Agenda
Note: all times are preliminary and flexible
Location: KHQ21 Conference Room
- 9:00 - Review/modify agenda
- 9:15 - Review/modify goals
- 9:30 - Establish baseline
- 9:45 - Assignments
- 10:00 - Hack, hack, submit reviews
Location: KHQ21 Auditorium
- 11:00 - Group Gerrit Review 1
- 12:00 - Lunch
- 13:00 - Hack, hack, submit reviews
- 15:00 - Group Gerrit Review 2
- 15:45 - Summary reports
- 16:30 - Action items
- 17:00 - Adjourn
Process
Define
What do we want to accomplish?
Measure
Failing Expected Nightly Tests
Analyze
This table summarize the failing tests and preliminary diagnosis.
Improve
Gerrit topics to fix failing tests.
Control
How to we keep things green?
