I like both approaches because maven won't necessarily find all problems if executed locally. Especially concurrency problems seem to occur more often on travis than on my local machine.
Greets, Till On Wed, Jan 21, 2015 at 9:59 AM, Max Michels <m...@data-artisans.com> wrote: > Hi Robert, > > I like your solution using Travis and Google App Engine. However, I > think there's a much simpler solution which can prevent commiters from > pushing not even compiling or test-failing code to the master in the > first place. > > Commiters could simply install a git pre-push hook in their git > repository (this is merely placing a file named pre-push in > .git/hooks/). The pre-push hook would simply run "mvn clean package" > and would then fail to push to the master if maven does not report > success. > > Such a precaution would save effort and time for everyone. You already > pointed out that not all eventualities are covered by the tests, so > this could be an additional measure to the Travis notifiction on the > dev mailing list. > > Best regards, > Max > > On Wed, Jan 21, 2015 at 12:30 AM, Ufuk Celebi <u...@apache.org> wrote: > > > > On 21 Jan 2015, at 00:19, Robert Metzger <rmetz...@apache.org> wrote: > > > >> I think its just a missing import. > > > > Yes. > > > >> Maybe we can use Google AppEngine for that. It seems that their free > >> offering is sufficient for our purpose: > >> https://cloud.google.com/pricing/#app-engine. It also allows sending > emails. > >> I guess its hard to get the token for the "apache" user. Maybe there is > is > >> a way to validate the authenticity of the requests differently. > > > > App engine sounds reasonable. :-) >
