The build-tools issue should be fixed now. Colm.
On Wed, Jan 13, 2016 at 7:24 AM, Zheng, Kai <[email protected]> wrote: > Thanks Stefan for lending the hand and I'm sorry for being late on this. > > >> But the build fails, the build-tools cannot be deployed because it > doesn't inherit from kerby-all parent pom > I don't quite understand how build-tools works and how to fix this. > > Maybe Colm or others could help with this? Thanks a lot. > > Regards, > Kai > > -----Original Message----- > From: Stefan Seelmann [mailto:[email protected]] > Sent: Wednesday, January 13, 2016 3:17 PM > To: [email protected] > Subject: Re: About Jenkins building on a branch > > > The Jenkins job that we (the PMC) can manage ourself [1] only triggers > > on changes on master (I think we need to change that to "trunk" now, > > right?). > > Changed it to 'trunk'. But the build fails, the build-tools cannot be > deployed because it doesn't inherit from kerby-all parent pom. > > > The one the builds branches is the one for Sonar [2]. This we cannot > > change ourself, but need to open a Jira. Which branch(es) should it > > build, I assume only "trunk"? > > Filed issue https://issues.apache.org/jira/browse/INFRA-11072 > > > [1] https://builds.apache.org/view/A-D/view/Directory/job/dir-kerby/ > > [2] https://analysis.apache.org/jenkins/job/directory-kerby/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
