You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Hugo Trippaers <hu...@trippaers.nl> on 2013/06/28 19:09:41 UTC
Jenkins and IRC
Heya,
I've added a parameterised job to jenkins that will run a complete build on any branch. You can kick it off on jenkins.cloudstack.org and enter any branch as the parameter. It will do the regular maven build with the clean and test actions. It will also generate a cobertura coverage report so you can easily see how much code your unit tests cover.
Also its possible to kick this build right from our IRC channel. For example the following command will build the vmsync branch:
!jenkins build cloudstack-build-parameterized now branch=vmsync
List the current builds using the '!jenkins cb' command.
So whenever you push a branch to apache, feel free to ask cato to build it for you.
Cheers,
Hugo
@David, remember that nginx proxy timeout setting we discussed ages ago? Would be nice to get that sorted so we can use some extra cloud power on jenkins.cloudstack.org. Any ideas on how we can get that done?
Re: Jenkins and IRC
Posted by Prasanna Santhanam <ts...@apache.org>.
On Mon, Jul 01, 2013 at 05:51:55PM +0200, Hugo Trippaers wrote:
> Heya,
>
> I "fixed" it manually for now. I've connected our cloud to the
> jenkins sytem. So there will be a few slaves popping up with names
> like 'cloudstack-buildslave-centos6-xxx'. These are automagically
> created by jenkins.
*dogfood* - gotta love it!
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Jenkins and IRC
Posted by Hugo Trippaers <hu...@trippaers.nl>.
Heya,
I "fixed" it manually for now. I've connected our cloud to the jenkins sytem. So there will be a few slaves popping up with names like 'cloudstack-buildslave-centos6-xxx'. These are automagically created by jenkins.
I've setup the cloudstack-master build to use these slaves in addition to the rpmbuilder, by setting the label expression. If this works we can add this label to more builds.
Cheers,
Hugo
On Jun 30, 2013, at 10:44 PM, David Nalley <da...@gnsa.us> wrote:
> On Sun, Jun 30, 2013 at 4:11 AM, Prasanna Santhanam <ts...@apache.org> wrote:
>> On Fri, Jun 28, 2013 at 10:25:47AM -0700, Hugo Trippaers wrote:
>>>>> @David, remember that nginx proxy timeout setting we discussed ages
>>>>> ago? Would be nice to get that sorted so we can use some extra cloud
>>>>> power on jenkins.cloudstack.org. Any ideas on how we can get that
>>>>> done?
>>>>
>>>> I plan on moving the current jenkins node on to a CloudStack setup
>>>> along with configuring jenkins purely via github/yaml config files.
>>>> still exploring. I think there should be some nginx puppet recipes
>>>> around for quick configuration.
>>>
>>> Nice! I still have some cloud power i can add to the jenkins pool in
>>> our cloud, so with all those clouds we should be able to speed
>>> things up.
>>
>> Yup - that's where we should be headed.
>>
>>>
>>> I tried making the change to the nginx configuration a while back,
>>> but some it did not get propagated, maybe you can have a look? This
>>> is my commit on the puppet module:
>>> https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5
>>
>> I don't know if the instance has been pulling config changes from
>> puppet anymore. It might need reviving. @David, is puppetmaster still
>> running for the cso-infra?
>>
>
> I don't believe it is - and I am hoping we move to a CloudStack-hosted
> Jenkins rather than the current one.
>
> --David
Re: Jenkins and IRC
Posted by David Nalley <da...@gnsa.us>.
On Sun, Jun 30, 2013 at 4:11 AM, Prasanna Santhanam <ts...@apache.org> wrote:
> On Fri, Jun 28, 2013 at 10:25:47AM -0700, Hugo Trippaers wrote:
>> >> @David, remember that nginx proxy timeout setting we discussed ages
>> >> ago? Would be nice to get that sorted so we can use some extra cloud
>> >> power on jenkins.cloudstack.org. Any ideas on how we can get that
>> >> done?
>> >
>> > I plan on moving the current jenkins node on to a CloudStack setup
>> > along with configuring jenkins purely via github/yaml config files.
>> > still exploring. I think there should be some nginx puppet recipes
>> > around for quick configuration.
>>
>> Nice! I still have some cloud power i can add to the jenkins pool in
>> our cloud, so with all those clouds we should be able to speed
>> things up.
>
> Yup - that's where we should be headed.
>
>>
>> I tried making the change to the nginx configuration a while back,
>> but some it did not get propagated, maybe you can have a look? This
>> is my commit on the puppet module:
>> https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5
>
> I don't know if the instance has been pulling config changes from
> puppet anymore. It might need reviving. @David, is puppetmaster still
> running for the cso-infra?
>
I don't believe it is - and I am hoping we move to a CloudStack-hosted
Jenkins rather than the current one.
--David
Re: Jenkins and IRC
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Jun 28, 2013 at 10:25:47AM -0700, Hugo Trippaers wrote:
> >> @David, remember that nginx proxy timeout setting we discussed ages
> >> ago? Would be nice to get that sorted so we can use some extra cloud
> >> power on jenkins.cloudstack.org. Any ideas on how we can get that
> >> done?
> >
> > I plan on moving the current jenkins node on to a CloudStack setup
> > along with configuring jenkins purely via github/yaml config files.
> > still exploring. I think there should be some nginx puppet recipes
> > around for quick configuration.
>
> Nice! I still have some cloud power i can add to the jenkins pool in
> our cloud, so with all those clouds we should be able to speed
> things up.
Yup - that's where we should be headed.
>
> I tried making the change to the nginx configuration a while back,
> but some it did not get propagated, maybe you can have a look? This
> is my commit on the puppet module:
> https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5
I don't know if the instance has been pulling config changes from
puppet anymore. It might need reviving. @David, is puppetmaster still
running for the cso-infra?
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Jenkins and IRC
Posted by Hugo Trippaers <hu...@trippaers.nl>.
On Jun 28, 2013, at 10:18 AM, Prasanna Santhanam <ts...@apache.org> wrote:
> On Fri, Jun 28, 2013 at 10:09:41AM -0700, Hugo Trippaers wrote:
>> Heya,
>>
>> I've added a parameterised job to jenkins that will run a complete
>> build on any branch. You can kick it off on jenkins.cloudstack.org
>> and enter any branch as the parameter. It will do the regular maven
>> build with the clean and test actions. It will also generate a
>> cobertura coverage report so you can easily see how much code your
>> unit tests cover.
>>
>> Also its possible to kick this build right from our IRC channel. For
>> example the following command will build the vmsync branch:
>>
>> !jenkins build cloudstack-build-parameterized now branch=vmsync
>>
>> List the current builds using the '!jenkins cb' command.
>>
>> So whenever you push a branch to apache, feel free to ask cato to
>> build it for you.
>
> Awesome! With Ian's help I plan to put in pretty Sonar graphs (if you
> like that sort of thing) as well for the static analysis checks.
>
>>
>> Cheers,
>>
>> Hugo
>>
>>
>> @David, remember that nginx proxy timeout setting we discussed ages
>> ago? Would be nice to get that sorted so we can use some extra cloud
>> power on jenkins.cloudstack.org. Any ideas on how we can get that
>> done?
>
> I plan on moving the current jenkins node on to a CloudStack setup
> along with configuring jenkins purely via github/yaml config files.
> still exploring. I think there should be some nginx puppet recipes
> around for quick configuration.
Nice! I still have some cloud power i can add to the jenkins pool in our cloud, so with all those clouds we should be able to speed things up.
I tried making the change to the nginx configuration a while back, but some it did not get propagated, maybe you can have a look? This is my commit on the puppet module: https://github.com/CloudStack-extras/cso-infrastructure/commit/9d65207989e7cbc5231f3f5184bd4bf6bf0f84d5
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
Re: Jenkins and IRC
Posted by Prasanna Santhanam <ts...@apache.org>.
On Mon, Jul 01, 2013 at 12:07:47PM -0400, Chip Childers wrote:
> On Mon, Jul 01, 2013 at 12:05:44PM -0400, John Burwell wrote:
> > Prasanna,
> >
> > I don't think a small namespace will deliver much value. We are
> > responsible for maintaining the code base -- even the older code
> > that will eventually be replaced. I would prefer to start with a
> > smaller set of rules focused on high priority issues (e.g. lack of
> > proper equals, hashCode, and toString implementations), fix them
> > across the entire codebase, and then expand the rule set. Wash,
> > rinse, repeat until we have a complete rule set and a compliant
> > code base.
> >
> > Thanks,
> > -John
>
> Same goal / different paths... FWIW, I'm with John. However, someone
> needs to propose the initial set of rules.
>
Works for me!
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Jenkins and IRC
Posted by Chip Childers <ch...@sungard.com>.
On Mon, Jul 01, 2013 at 12:05:44PM -0400, John Burwell wrote:
> Prasanna,
>
> I don't think a small namespace will deliver much value. We are responsible for maintaining the code base -- even the older code that will eventually be replaced. I would prefer to start with a smaller set of rules focused on high priority issues (e.g. lack of proper equals, hashCode, and toString implementations), fix them across the entire codebase, and then expand the rule set. Wash, rinse, repeat until we have a complete rule set and a compliant code base.
>
> Thanks,
> -John
Same goal / different paths... FWIW, I'm with John. However, someone
needs to propose the initial set of rules.
>
> On Jun 29, 2013, at 2:12 AM, Prasanna Santhanam <ts...@apache.org> wrote:
>
> > On Fri, Jun 28, 2013 at 02:45:02PM -0400, John Burwell wrote:
> >> Prasanna,
> >>
> >> I am all for static analysis, but I think we should discuss it before
> >> implementation to ensure that the community is in sync on the rules
> >> and priority. I am of the belief that static analysis shouldn't check
> >> for violations that we don't are worthy of breaking a build. However,
> >> implementing such an approach would take a fair amount if coordination
> >> and effort for (needed) cleanup.
> >
> > Sure - we can start with a small namespace, say
> > org.apache.cloudstack.storage, and extend the envelope based on
> > discussions. Makes sense?
> >
> >>
> >> That's my $0.02,
> >> -John
> >>
> > --
> > Prasanna.,
> >
> > ------------------------
> > Powered by BigRock.com
> >
>
>
Re: Jenkins and IRC
Posted by John Burwell <jb...@basho.com>.
Prasanna,
I don't think a small namespace will deliver much value. We are responsible for maintaining the code base -- even the older code that will eventually be replaced. I would prefer to start with a smaller set of rules focused on high priority issues (e.g. lack of proper equals, hashCode, and toString implementations), fix them across the entire codebase, and then expand the rule set. Wash, rinse, repeat until we have a complete rule set and a compliant code base.
Thanks,
-John
On Jun 29, 2013, at 2:12 AM, Prasanna Santhanam <ts...@apache.org> wrote:
> On Fri, Jun 28, 2013 at 02:45:02PM -0400, John Burwell wrote:
>> Prasanna,
>>
>> I am all for static analysis, but I think we should discuss it before
>> implementation to ensure that the community is in sync on the rules
>> and priority. I am of the belief that static analysis shouldn't check
>> for violations that we don't are worthy of breaking a build. However,
>> implementing such an approach would take a fair amount if coordination
>> and effort for (needed) cleanup.
>
> Sure - we can start with a small namespace, say
> org.apache.cloudstack.storage, and extend the envelope based on
> discussions. Makes sense?
>
>>
>> That's my $0.02,
>> -John
>>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
Re: Jenkins and IRC
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Jun 28, 2013 at 02:45:02PM -0400, John Burwell wrote:
> Prasanna,
>
> I am all for static analysis, but I think we should discuss it before
> implementation to ensure that the community is in sync on the rules
> and priority. I am of the belief that static analysis shouldn't check
> for violations that we don't are worthy of breaking a build. However,
> implementing such an approach would take a fair amount if coordination
> and effort for (needed) cleanup.
Sure - we can start with a small namespace, say
org.apache.cloudstack.storage, and extend the envelope based on
discussions. Makes sense?
>
> That's my $0.02,
> -John
>
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Jenkins and IRC
Posted by John Burwell <jb...@basho.com>.
Prasanna,
I am all for static analysis, but I think we should discuss it before
implementation to ensure that the community is in sync on the rules
and priority. I am of the belief that static analysis shouldn't check
for violations that we don't are worthy of breaking a build. However,
implementing such an approach would take a fair amount if coordination
and effort for (needed) cleanup.
That's my $0.02,
-John
On Jun 28, 2013, at 1:19 PM, Prasanna Santhanam <ts...@apache.org> wrote:
> On Fri, Jun 28, 2013 at 10:09:41AM -0700, Hugo Trippaers wrote:
>> Heya,
>>
>> I've added a parameterised job to jenkins that will run a complete
>> build on any branch. You can kick it off on jenkins.cloudstack.org
>> and enter any branch as the parameter. It will do the regular maven
>> build with the clean and test actions. It will also generate a
>> cobertura coverage report so you can easily see how much code your
>> unit tests cover.
>>
>> Also its possible to kick this build right from our IRC channel. For
>> example the following command will build the vmsync branch:
>>
>> !jenkins build cloudstack-build-parameterized now branch=vmsync
>>
>> List the current builds using the '!jenkins cb' command.
>>
>> So whenever you push a branch to apache, feel free to ask cato to
>> build it for you.
>
> Awesome! With Ian's help I plan to put in pretty Sonar graphs (if you
> like that sort of thing) as well for the static analysis checks.
>
>>
>> Cheers,
>>
>> Hugo
>>
>>
>> @David, remember that nginx proxy timeout setting we discussed ages
>> ago? Would be nice to get that sorted so we can use some extra cloud
>> power on jenkins.cloudstack.org. Any ideas on how we can get that
>> done?
>
> I plan on moving the current jenkins node on to a CloudStack setup
> along with configuring jenkins purely via github/yaml config files.
> still exploring. I think there should be some nginx puppet recipes
> around for quick configuration.
>
> --
> Prasanna.,
>
> ------------------------
> Powered by BigRock.com
>
Re: Jenkins and IRC
Posted by Prasanna Santhanam <ts...@apache.org>.
On Fri, Jun 28, 2013 at 10:09:41AM -0700, Hugo Trippaers wrote:
> Heya,
>
> I've added a parameterised job to jenkins that will run a complete
> build on any branch. You can kick it off on jenkins.cloudstack.org
> and enter any branch as the parameter. It will do the regular maven
> build with the clean and test actions. It will also generate a
> cobertura coverage report so you can easily see how much code your
> unit tests cover.
>
> Also its possible to kick this build right from our IRC channel. For
> example the following command will build the vmsync branch:
>
> !jenkins build cloudstack-build-parameterized now branch=vmsync
>
> List the current builds using the '!jenkins cb' command.
>
> So whenever you push a branch to apache, feel free to ask cato to
> build it for you.
Awesome! With Ian's help I plan to put in pretty Sonar graphs (if you
like that sort of thing) as well for the static analysis checks.
>
> Cheers,
>
> Hugo
>
>
> @David, remember that nginx proxy timeout setting we discussed ages
> ago? Would be nice to get that sorted so we can use some extra cloud
> power on jenkins.cloudstack.org. Any ideas on how we can get that
> done?
I plan on moving the current jenkins node on to a CloudStack setup
along with configuring jenkins purely via github/yaml config files.
still exploring. I think there should be some nginx puppet recipes
around for quick configuration.
--
Prasanna.,
------------------------
Powered by BigRock.com
Re: Jenkins and IRC
Posted by Rohit Yadav <bh...@apache.org>.
On Fri, Jun 28, 2013 at 10:39 PM, Hugo Trippaers <hu...@trippaers.nl> wrote:
> Heya,
>
> I've added a parameterised job to jenkins that will run a complete build
> on any branch. You can kick it off on jenkins.cloudstack.org and enter
> any branch as the parameter. It will do the regular maven build with the
> clean and test actions. It will also generate a cobertura coverage report
> so you can easily see how much code your unit tests cover.
>
> Also its possible to kick this build right from our IRC channel. For
> example the following command will build the vmsync branch:
>
> !jenkins build cloudstack-build-parameterized now branch=vmsync
>
> List the current builds using the '!jenkins cb' command.
>
> So whenever you push a branch to apache, feel free to ask cato to build it
> for you.
>
w00t! awesome.
>
> Cheers,
>
> Hugo
>
>
> @David, remember that nginx proxy timeout setting we discussed ages ago?
> Would be nice to get that sorted so we can use some extra cloud power on
> jenkins.cloudstack.org. Any ideas on how we can get that done?