I've reverted to the old-style way of finding the pmd + checkstyle files using profiles. In the future, we can consider releasing them as a separate project, but for now I think this is not necessary.
Colm. On Sun, Jan 17, 2016 at 10:21 PM, Zheng, Kai <[email protected]> wrote: > Thanks Stefan for the quick response and helpful clarifying!! I just went > asleep again. :) > > >> The jobs are configured that only build failures trigger a mail. > I thought the current criteria looks reasonable. I just realized, the > building is daily, when it's failed, there will be a mail to notify. When > the building failure is fixed and the building on the next day passes, > there will also be a mail to notify "back to normal". So no change is > needed and your consideration is reasonable, this is great. > > >> I don't think it's complicated to handle, but may need a bit of > trial-and-error. > I'm glad we can keep build-tool module since it can be fixed for the > release. When the project becomes big, there may be complicated things to > put in the separate module. > > >>When do you plan to do the next release? > No concrete plan yet. I may have some spare time, resume some related > discussions and do some work in this week for the release. After laying out > some basic structures and codes for kadmin-remote, contributors like Yan > could work on it in the branch separately. So in my side, Jiajia and I can > do the required changes for the release on trunk. I hope it won't be too > much but the time is also limited, considering there is going to be a long > Spring Festival holiday in the beginning of next month in PRC China. > > >>Then I'll try to help figuring out the right procedure. > Thanks thanks for the taking! > > Regards, > Kai > > -----Original Message----- > From: Stefan Seelmann [mailto:[email protected]] > Sent: Monday, January 18, 2016 4:28 AM > To: [email protected] > Subject: Re: About Jenkins building on a branch > > Hi Kai, > > On 01/17/2016 09:03 PM, Zheng, Kai wrote: > > Hi Stefan and Colm, > > > > There has been days that we haven't received any Jenkins building on the > trunk branch now. We need to bring it back ASAP. > > We didn't receive anything because the build is successful, see [1] and > [2]. The jobs are configured that only build failures trigger a mail. I > think that makes sense to not flood our inboxes. Or do you want to receive > a mail on every build? > > > Was this issue cause by the change from master to trunk, or the change > of having build-tools? > > > > The involving of two steps in the release process for each release looks > a bit complicated. > > The issue I described doesn't apply to the snapshot build on Jenkins but > only when creating a release (I think). I don't think it's complicated to > handle, but may need a bit of trial-and-error. When do you plan to do the > next release? Then I'll try to help figuring out the right procedure. > > Kind Regards, > Stefan > > > [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-kerby/ > [2] > > https://analysis.apache.org/jenkins/view/directory-projects/job/directory-kerby/ > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
