You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kerby@directory.apache.org by "Zheng, Kai" <ka...@intel.com> on 2016/01/11 13:58:06 UTC
About Jenkins building on a branch
Hi Stefan,
I'm wondering if it's necessary to trigger Jenkins building on a Kerby branch, considering the current status of the project. Could we not do that? Thanks for the help.
Regards,
Kai
Re: About Jenkins building on a branch
Posted by Colm O hEigeartaigh <co...@apache.org>.
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 <ka...@intel.com> 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:mail@stefan-seelmann.de]
> Sent: Monday, January 18, 2016 4:28 AM
> To: kerby@directory.apache.org
> 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
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
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:mail@stefan-seelmann.de]
Sent: Monday, January 18, 2016 4:28 AM
To: kerby@directory.apache.org
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/
Re: About Jenkins building on a branch
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
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/
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
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. Should we revert the build-tools change (remove the module) for the fixup? Please help confirm, thanks.
Regards,
Kai
-----Original Message-----
From: Zheng, Kai [mailto:kai.zheng@intel.com]
Sent: Saturday, January 16, 2016 4:58 PM
To: kerby@directory.apache.org
Subject: RE: About Jenkins building on a branch
Thanks Stefan for the solution.
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.
Regards,
Kai
-----Original Message-----
From: Stefan Seelmann [mailto:mail@stefan-seelmann.de]
Sent: Thursday, January 14, 2016 3:24 AM
To: kerby@directory.apache.org
Subject: Re: About Jenkins building on a branch
On 01/13/2016 12:58 PM, Colm O hEigeartaigh wrote:
> The build-tools issue should be fixed now.
Thanks Colm for the fix. However I'm afraid that won't work well when doing a release using the maven-release-plugin. As build-tools doesn't have kerby-all as parent I think it won't be included when setting the release version.
I think the only solution is to release the build-tools first as separate project. Then the release version can be used in kerby-all and removed from the aggregator build.
Kind Regards,
Stefan
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
Thanks Stefan for the solution.
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.
Regards,
Kai
-----Original Message-----
From: Stefan Seelmann [mailto:mail@stefan-seelmann.de]
Sent: Thursday, January 14, 2016 3:24 AM
To: kerby@directory.apache.org
Subject: Re: About Jenkins building on a branch
On 01/13/2016 12:58 PM, Colm O hEigeartaigh wrote:
> The build-tools issue should be fixed now.
Thanks Colm for the fix. However I'm afraid that won't work well when doing a release using the maven-release-plugin. As build-tools doesn't have kerby-all as parent I think it won't be included when setting the release version.
I think the only solution is to release the build-tools first as separate project. Then the release version can be used in kerby-all and removed from the aggregator build.
Kind Regards,
Stefan
Re: About Jenkins building on a branch
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 01/13/2016 12:58 PM, Colm O hEigeartaigh wrote:
> The build-tools issue should be fixed now.
Thanks Colm for the fix. However I'm afraid that won't work well when
doing a release using the maven-release-plugin. As build-tools doesn't
have kerby-all as parent I think it won't be included when setting the
release version.
I think the only solution is to release the build-tools first as
separate project. Then the release version can be used in kerby-all and
removed from the aggregator build.
Kind Regards,
Stefan
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
Your fix looks magic to me. Cool. Thanks Colm.
Regards,
Kai
-----Original Message-----
From: Colm O hEigeartaigh [mailto:coheigea@apache.org]
Sent: Wednesday, January 13, 2016 7:58 PM
To: kerby@directory.apache.org
Subject: Re: About Jenkins building on a branch
The build-tools issue should be fixed now.
Colm.
On Wed, Jan 13, 2016 at 7:24 AM, Zheng, Kai <ka...@intel.com> 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:mail@stefan-seelmann.de]
> Sent: Wednesday, January 13, 2016 3:17 PM
> To: kerby@directory.apache.org
> 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
Re: About Jenkins building on a branch
Posted by Colm O hEigeartaigh <co...@apache.org>.
The build-tools issue should be fixed now.
Colm.
On Wed, Jan 13, 2016 at 7:24 AM, Zheng, Kai <ka...@intel.com> 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:mail@stefan-seelmann.de]
> Sent: Wednesday, January 13, 2016 3:17 PM
> To: kerby@directory.apache.org
> 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
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
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:mail@stefan-seelmann.de]
Sent: Wednesday, January 13, 2016 3:17 PM
To: kerby@directory.apache.org
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/
Re: About Jenkins building on a branch
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
> 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/
RE: About Jenkins building on a branch
Posted by "Zheng, Kai" <ka...@intel.com>.
Thanks Stefan for the helpful information and I will learn about it.
Yes we need to switch to trunk from master and we wouldn't trigger the Jenkins on other branches in the current situation.
Regards,
Kai
-----Original Message-----
From: Stefan Seelmann [mailto:mail@stefan-seelmann.de]
Sent: Tuesday, January 12, 2016 3:18 AM
To: kerby@directory.apache.org
Subject: Re: About Jenkins building on a branch
Hi Kai,
On 01/11/2016 01:58 PM, Zheng, Kai wrote:
> I'm wondering if it's necessary to trigger Jenkins building on a Kerby branch, considering the current status of the project. Could we not do that? Thanks for the help.
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?).
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"?
Kind Regards,
Stefan
[1] https://builds.apache.org/view/A-D/view/Directory/job/dir-kerby/
[2] https://analysis.apache.org/jenkins/job/directory-kerby/
Re: About Jenkins building on a branch
Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Hi Kai,
On 01/11/2016 01:58 PM, Zheng, Kai wrote:
> I'm wondering if it's necessary to trigger Jenkins building on a Kerby branch, considering the current status of the project. Could we not do that? Thanks for the help.
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?).
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"?
Kind Regards,
Stefan
[1] https://builds.apache.org/view/A-D/view/Directory/job/dir-kerby/
[2] https://analysis.apache.org/jenkins/job/directory-kerby/