Details
-
User Story
-
Resolution: Done
-
P2: Important
-
None
-
None
-
5
-
a85c52dbc32412cf3adba34dd5c1f0d90dcdb621
Description
I am thinking of this scenario:
- there are 30 staged changes
- they all move to INTEGRATING state, and testing begins
- testing fails with some bogus error, like a temporary DNS failure
- all the changes are unstaged, with some details about the error added as a comment
- CI system sends an email to CI admins
Since it is obvious to the CI admins that it was a bogus error, it makes sense that we would re-stage all the changes.
However this will be extremely cumbersome at the moment, as we have no practical way to enumerate all the changes which were affected.
I suggest that the CI mails are extended so that the "Integration summary" part, which is currently not too useful in the gerrit case, is replaced with links to the gerrit changes. e.g.
This is an automated report from the Qt Continuous Integration System
Error: Build failure
Source: qt/qt-integration.git#qt-4.8-from-4.7
Dest: qt/qt.git#4.8
SHA1: c09b481edd82942cdc85d138c2160004bd71a54e
More details about this problem:
stage: symbian-armcc 5.0-gnupoc-stripped-stable on Ubuntu 10.04 x86 on bq-ubuntu1004-x86-31
Build or test procedure failed
make[1]: *** No rule to make target `aknicon.dso', needed by `../../lib/QtGui.dll'. Stop.
Build log:
http://pulse.test.qt.nokia.com/browse/projects/Qt%20master%20Integration/builds/1695/logs/stage/symbian-armcc%205.0-gnupoc-stripped-stable%20on%20
Ubuntu%2010.04%20x86/raw/true/
Tested changes:
http://codereview.qt.nokia.com/115 - fix "Host" header of ipv6 URLs in QNAM
http://codereview.qt.nokia.com/126 - Add QtTools' include/QtDesigner as well as QtCore's include/QtDesigner
(... etc)
Then we can easily follow the links and re-stage the changes.