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 e
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.
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 rul
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, hashCod
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
On Sun, Jun 30, 2013 at 4:11 AM, Prasanna Santhanam 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.c
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?
> >
>
On Fri, Jun 28, 2013 at 10:39 PM, 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
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 v
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,
implemen
On Jun 28, 2013, at 10:18 AM, Prasanna Santhanam 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 bran
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
12 matches
Mail list logo
