Re: Master build failing with compilation error

Hi, Will check and fix it today. Regards. On 29-Aug-2014, at 2:53 am, Amogh Vasekar wrote: > Hi, > Seems is failing after the SAML2 branch merge : See > > Have pushed in a temp fix, will check again to see what may have ex

[DISCUSS] Prevent force push on release and master branches

Hi all, I found by accident that you can force push on branches on our ACS/ASF repo. So, I’m concerned that anyone could do a force push, sneak in changes on ACS/ASF branches; opensource projects have had issues with people changing histories, putting backdoors and whatnot, so I would like to a

Re: [DISCUSS] Prevent force push on release and master branches

> So, I’m told that we need to discuss this issue and only after a decision/voting they would implement such a change? What do you think, what are the pros and cons of disabling force pushes and should we do it? Definitely a +1 on disabling. forced pushing in my view should be never used on a publ

Fwd: [NOTICE] JIRA downtime this weekend

FYI -- Forwarded message -- From: Mark Thomas Date: Fri, Aug 29, 2014 at 8:21 AM Subject: [NOTICE] JIRA downtime this weekend To: "infrastruct...@apache.org" All, We have identified the root cause of the long running requests (that are at least partially responsible for recen

cloudstack-checkstyle

How are we supposed to verify and fix the cloudstack-checkstyle errors? The stack traces do not give any feedback at all for where the error occurred so it is basically impossible to have a good code/test/fix cycle with it. Any ideas??? *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutio

Review Request 25187: test_delete_account and test_releaseIP failing in advanced zone

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/25187/ --- Review request for cloudstack, Ashutosh Kelkar and Santhosh Edukulla. Bugs: CLO

Re: [DISCUSS] Prevent force push on release and master branches

+1 Rewrite history on a public repo opens the door for very catastrophic situations. On Fri, Aug 29, 2014 at 7:23 AM, Ian Duffy wrote: > > So, I’m told that we need to discuss this issue and only after a > decision/voting they would implement such a change? What do you think, what > are the pro

Re: cloudstack-checkstyle

They don't? I've always been able to find something in the maven output pointing to a line with trailing spaces or something. It just isn't the very last thing it prints. If you're not compiling multi-threaded (e.g. mvn -T C1.5) then it's usually 100 or so lines up, above the report. If you ARE m

Re: cloudstack-checkstyle

Thank you. Yes, I was able to find it. It was not in the stacktrace, but there was a single line above the report which gave me info as to why it failed. Thx, Will *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.

Unable to connect to management server on current master builds

Hello all, On current master builds (such as http://jenkins.buildacloud.org/job/package-rhel63-master/3202/), I can't connect to the management server, either via the API or UI. The major changes since the last working build I had seems to be the SAML2 merge (there are a couple of other things

[ACS4.4.1] Cherry-Pick fix for CLOUDSTACK-7124

Hi, Any chance we could cherry-pick the commit from master to fix CLOUDSTACK-7124 on 4.4.1? We are also impacted. Thanks! -- Francois Gaudreault Gestionnaire de Produit | Product Manager - Cloud Platform & Services t:514-629-6775 CloudOps Votre partenaire infonuagique | Cloud Solutions Exper

Re: [DISCUSS] Prevent force push on release and master branches

force pushes on master are already prohibited. The other branches allow that though. --David On Fri, Aug 29, 2014 at 7:57 AM, Rohit Yadav wrote: > Hi all, > > I found by accident that you can force push on branches on our ACS/ASF repo. > > So, I’m concerned that anyone could do a force push, sne

Re: [DISCUSS] Prevent force push on release and master branches

Hi David, On 29-Aug-2014, at 6:59 pm, David Nalley wrote: > force pushes on master are already prohibited. > The other branches allow that though. We already know this. The discussion is; 1. Should we put git hooks to prevent force pushes on all branches? (people would be still able to delete

Re: Review Request 22706: This test suite contains test cases relating to access checks for listVolume() with parameters - id, listall, isrecursive, account and domainid executed as ROOT admin, domain

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22706/#review51924 --- Looks good to me, thanks for writting up this test cases, it's reall

Re: Review Request 22706: This test suite contains test cases relating to access checks for listVolume() with parameters - id, listall, isrecursive, account and domainid executed as ROOT admin, domain

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/22706/#review51928 --- Ship it! Ship It! - edison su On Aug. 28, 2014, 12:56 a.m., sang

Re: [DISCUSS] Prevent force push on release and master branches

+1 on disable force push. On 8/29/14, 8:39 AM, Nate Gordon wrote: +1 Rewrite history on a public repo opens the door for very catastrophic situations. On Fri, Aug 29, 2014 at 7:23 AM, Ian Duffy wrote: So, I’m told that we need to discuss this issue and only after a decision/voting they wou

[BLOCKED] Unable to connect to management server on current master builds

CC Rohit here in case he didn't see this email. Rohit, can you fix this? Thanks -min On 8/29/14 9:21 AM, "Alex Brett" wrote: >Hello all, > >On current master builds (such as >http://jenkins.buildacloud.org/job/package-rhel63-master/3202/), I can't >connect to the management server, either via

Re: S3/Swift Problem around Virtual Size

That's a good question, Marcus. I've CCed Edison to bring this to his attention. Edison - What do you think? Thanks On Tue, Aug 26, 2014 at 9:48 PM, Marcus wrote: > Per Edisons comments about not knowing the image size, can't we just set > some headers and store metadata with the template in

Re: [DISCUSS] Prevent force push on release and master branches

Projects do not have the ability to specify their own hooks. You essentially get the same set as every other project in the Foundation using git. The reasons behind this are that essentially projects would have an incredibly divergent set of hooks, they would be unmaintainable long term. Infra has