[aerogear-dev] How to propagate results for non Travis CI?

Douglas Campos qmx at qmx.me
Tue Sep 24 13:06:32 EDT 2013


On Tue, Sep 24, 2013 at 06:30:34PM +0200, Karel Piwko wrote:
> > > * When to notify? [failure only|unstable|always]
> > 
> > Failure only
> Sorry, I was not explicit here:
> * Failure: job didn't finish (aborted to to some error)
> * Unstable: some tests failed
> 
> What about specific states, like still-failing or still-unstable?

The less noise, the better - I think jenkins has a "state changed only"
notification setting

> > 
> > > * How often to run tests? [nightly|per commit]
> > 
> > This really boils down to what kind of tests are being run, and how busy
> > is the build-slave queue.
> 
> Well, per commit strategy is unrealistic setup when trying to rerun everyting.

So nightly is the obvious choice, right?
> 
> > 
> > > * How to enable developers to easily rerun something? [email|irc]
> > 
> > irc would be easier, email safer?
> 
> I prefer IRC, however QE does not cover all timezones. In such cases email
> makes more sense.

Aaah, will it be manual intervention? email then.

-- 
qmx


More information about the aerogear-dev mailing list