[yast-devel] CI and email when build fails
Hi, I start setting up jobs for adapted modules in public ci.opensuse.org Question is wheere should it write email when build fail. Options are: 1) Only to person who broke it 2) also to some mailing list (yast-commit or yast-devel) 3) other mail address ( which one?) Without it I worry that it take some time until we notice that something is broken. Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Wed, Oct 02, 2013 at 03:37:58PM +0200, Josef Reidinger wrote:
Hi, I start setting up jobs for adapted modules in public ci.opensuse.org Question is wheere should it write email when build fail. Options are: 1) Only to person who broke it 2) also to some mailing list (yast-commit or yast-devel)
I vote for this list, yast-devel. The check done in jenkins is designed simple enough that people should be able to run it locally before pushing, so failures should be rare enough. Which also reminds me that yast-commit is too much for me to even skim. 413, 982, 306, 375 mails in the last months. http://lists.opensuse.org/yast-commit/2013-09/date.html
3) other mail address ( which one?) -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Dne 2.10.2013 15:37, Josef Reidinger napsal(a):
Hi, I start setting up jobs for adapted modules in public ci.opensuse.org Question is wheere should it write email when build fail. Options are: 1) Only to person who broke it
Not a good idea as e.g. broken commit in yast2 can break some other module, the fix might be urgent (when braking all yast modules), or the author might just has left for vacation, etc...
2) also to some mailing list (yast-commit or yast-devel)
yast-commit is the best IMHO, yast-devel should be for discussions (for people, not for bots).
3) other mail address ( which one?)
I don't think there is a better ML, definitely do not create new YaML (Yet another Mailing List ;-) ).
Without it I worry that it take some time until we notice that something is broken.
I fully agree. -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 10/04/2013 05:03 PM, Ladislav Slezak wrote:
Dne 2.10.2013 15:37, Josef Reidinger napsal(a):
Hi, I start setting up jobs for adapted modules in public ci.opensuse.org Question is wheere should it write email when build fail. Options are: 1) Only to person who broke it
Not a good idea as e.g. broken commit in yast2 can break some other module, the fix might be urgent (when braking all yast modules), or the author might just has left for vacation, etc...
+1
2) also to some mailing list (yast-commit or yast-devel)
yast-commit is the best IMHO, yast-devel should be for discussions (for people, not for bots).
+1
3) other mail address ( which one?)
I don't think there is a better ML, definitely do not create new YaML (Yet another Mailing List ;-) ).
+1 Thx Lukas -- Lukas Ocilka, Cloud & Systems Management Department SUSE LINUX s.r.o., Praha -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (4)
-
Josef Reidinger -
Ladislav Slezak -
Lukas Ocilka -
Martin Vidner