Follow us on Google+ Follow us on Facebook Follow us on Twitter

Opened 8 years ago

Closed 2 weeks ago

#126 closed enhancement (fixed)

Breakage and regression monitoring tool

Reported by: Jiri Svoboda Owned by:
Priority: minor Milestone:
Component: web Version: mainline
Keywords: gsoc10, gsoc11 Cc:
Blocker for: Depends on: #124
See also:

Description (last modified by Jakub Jermář)

Implement a web-based framework that would monitor build breakages and functional regressions introduced to the HelenOS development tree.

Details
The framework would periodically build the newest revision of the HelenOS sources for all supported targets and report back potential build problems. The periodicity should be configurable to happen after each integration or in some fixed intervals such as on the nightly basis. Depending on the periodicity, the framework should be able to either point to the exact changeset which introduced the breakage or at least say the breakage was introduced between revisions X and Y.

The second major role of the framework would be to consecutively run the built system images in a suitable simulator such as Qemu, run automated regression tests inside HelenOS and store the results on a disk from where they could be read by the framework and published via a web interface. As in the previous case, the framework should be able to figure out what revision made some testcase fail.

This project depends on:

#124 Hands-off configure/build

What Gains and Benefits will this bring?
With the help of a tool like this, we should be able to catch most regressions and breakages much earlier than we do now. A person who neglects to test his changes on all supported platforms will automatically learn about the problem immediately or the other day at the latest.
Difficulty
medium
Required skills
A successful applicant should be able to integrate several products together.
Documentation
Possible mentors
HelenOS Core Team, Martin Decky, Jiri Svoboda

Change History (16)

comment:1 Changed 8 years ago by Jakub Jermář

Component: unspecifiedweb
Description: modified (diff)
Keywords: gsoc added
Summary: Automated regression monitoringBreakage and regression monitoring tool

comment:2 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:3 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:4 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:5 Changed 8 years ago by Martin Decky

Description: modified (diff)

comment:6 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:7 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:8 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:9 Changed 8 years ago by Jakub Jermář

Description: modified (diff)

comment:10 Changed 7 years ago by Jakub Jermář

Keywords: gsoc10 gsoc11 added; gsoc removed

comment:11 Changed 7 years ago by Jakub Jermář

Depends on: #124
Keywords: gsoc10,gsoc11gsoc10, gsoc11

comment:12 Changed 7 years ago by Jakub Jermář

Milestone: 0.5.00.5.1

comment:13 Changed 7 years ago by Jakub Jermář

Keywords: gsoc10, gsoc11gsoc10, gsoc11

comment:14 Changed 6 years ago by Jakub Jermář

Milestone: 0.5.0

comment:15 Changed 3 years ago by Jakub Jermář

Vojta has put together the following continuous integration page:

http://helenos.alisma.cz/jenkins/

comment:16 Changed 2 weeks ago by Jiri Svoboda

Resolution: fixed
Status: newclosed

HelenOS CI now lives at http://ci.helenos.org/
I think it solves this ticket.

Note: See TracTickets for help on using tickets.