On Thu, 12 Sep 2013 10:39:17 +0200 Ladislav Slezak <[email protected]> wrote:
> Dne 11.9.2013 15:10, Lukas Ocilka napsal(a): > [...] > > All maintained branches would make sense. That's the only way how > > we can make sure nothing breaks by our change somewhere. > > Additionally, once a week (for instance), all the checks could be > > rerun even if no Yast packages were changed - it's because of the > > possible environment changes. > > I do not think we need to run the test "just in case" every week. The > tests are run during package build so if there is detected any change > outside Yast the build service will trigger rebuild (via package > dependencies) and the tests will be re-run. > > The only difference is that Jenkins sends mails on failures while OBS > does not. > We can setup hermes to send mails to yast-devel or yast-commit in case of failures so even obs can send mails. Josef > -- > > Best Regards > > Ladislav Slezák > Yast Developer > ------------------------------------------------------------------------ > SUSE LINUX, s.r.o. e-mail: > [email protected] Lihovarská 1060/12 tel: > +420 284 028 960 190 00 Prague 9 fax: > +420 284 028 951 Czech Republic > http://www.suse.cz/ -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
