Yes we should address the current depts first. When possible, add the checks you listed one by one. Thanks!
Regards, Kai -----Original Message----- From: Stefan Seelmann [mailto:[email protected]] Sent: Thursday, July 02, 2015 6:11 AM To: [email protected] Subject: Re: Jenkins job for Kerby I agree, Colm already added PMD check. Probably we can add checkstyle, findbugs, and test coverage (JaCoCo) checks too. Otherwise Sonar https://analysis.apache.org/dashboard/index/212397 shows current "depts". Kind Regards, Stefan On 07/02/2015 12:01 AM, Zheng, Kai wrote: > Yeah daily is good enough for now. The TZ is OK for me. Kerby is building > fast and easily on developer's machine so per-commit building should be done > by the developer before the commit. > I thought one further ting could be to let the building perform more > checking, one example for coding styles, like Emmanuel pointed out, Javadocs > shouldn't be missed ... > > Regards, > Kai > > -----Original Message----- > From: Stefan Seelmann [mailto:[email protected]] > Sent: Thursday, July 02, 2015 5:47 AM > To: [email protected] > Subject: Re: Jenkins job for Kerby > > Oh yes, forgot to mention that. > > The build is triggered once daily a 4:00 UTC. Maybe another time that better > suites your timezone makes sense? > > We can also build per commit (not sure if push is possible from Apache git, > otherwise poll is required). > > I'd avoid to setup something like Hadoops pre-commit-patch-test-thingy > until Kerby has 50 developers ;) > > Kind Regards, > Stefan > > > On 07/01/2015 11:26 PM, Zheng, Kai wrote: >> Thanks Stefan a lot for the taking!! It's great. How is the building >> triggered? Or just daily? Per commit triggering like Hadoop may be heavy for >> now ... >> >> Regards, >> Kai >> >> -----Original Message----- >> From: Stefan Seelmann [mailto:[email protected]] >> Sent: Thursday, July 02, 2015 4:38 AM >> To: [email protected] >> Subject: Jenkins job for Kerby >> >> Hi, >> >> there is now a working Jenkins job for Kerby [1] >> >> Until there is a JDK with unilimited security available on Jenkins [2] some >> tests are ignored, I added JUnit's assumptions to the relevant test cases. >> >> Notications about failed build currently go to >> [email protected], if wished we can also send them to this >> list. >> >> Kind Regards, >> Stefan >> >> [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-kerby/ >> [2] https://issues.apache.org/jira/browse/BUILDS-86 >> >
