Looks like http://repository.jboss.org/nexus/content/groups/public-jboss is having problems.
I will just wait for it to come back. On Thu, Apr 18, 2013 at 5:25 PM, Andrew Purtell <apurt...@apache.org> wrote: > Hi Ted, > > Why are you asking me this? Do you think this is a problem with EC2 > Jenkins? Did you check repository.jboss.org ? Does it work for you? This > is what I get at > > http://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/apache/12/apache-12-site_en.xml > : > > Service Temporarily Unavailable > > The server is temporarily unable to service your request due to maintenance > downtime or capacity problems. Please try again later. > ------------------------------ > Apache Server at repository.jboss.org Port 80 > > > > > On Thu, Apr 18, 2013 at 5:22 PM, Ted Yu <yuzhih...@gmail.com> wrote: > > > Andy: > > Have you noticed the following from recent EC2 trunk builds ? > > > > cause : SiteToolException: The site descriptor cannot be resolved from > the > > repository: ArtifactResolutionException: Unable to locate site > descriptor: > > Could not transfer artifact org.apache:apache:xml:site_en:12 from/to > > repository.jboss.org ( > > http://repository.jboss.org/nexus/content/groups/public-jboss/): Failed > to > > transfer file: > > > > > http://repository.jboss.org/nexus/content/groups/public-jboss/org/apache/apache/12/apache-12-site_en.xml > > . > > Return code is: 503, ReasonPhrase:Service Temporarily Unavailable. > > org.apache:apache:xml:12 > > > > On Thu, Apr 18, 2013 at 12:46 PM, Andrew Purtell <apurt...@apache.org > > >wrote: > > > > > Today I updated the EC2 plugin to see if that resolves the issue with > > > occasional failed slave launches. It looks good so far. > > > > > > > > > On Thu, Mar 21, 2013 at 9:38 PM, Stack <st...@duboce.net> wrote: > > > > > > > This machine is now running builds: http://54.241.6.143/ After > some > > > > messing to fix memory allocation, it seems tests are failing > > legitimately > > > > now for both 0.94 and trunk. They warrant fixing (thanks for > setting > > > this > > > > up Andrew). > > > > St.Ack > > > > > > > > > > > > On Tue, Mar 19, 2013 at 10:48 AM, Andrew Purtell < > apurt...@apache.org > > > > >wrote: > > > > > > > > > I have checked with the folks here and until/unless the situation > > with > > > > ASF > > > > > Jenkins VMs improves, we can provide a hosted Jenkins up in EC2, in > > > > > us-west-1: > > > > > > > > > > - A m1.large instance running 24/7 hosting Jenkins > > > > > > > > > > - A pool of 5 m1.large instances serving as Jenkins slaves, > managed > > > by > > > > > Jenkins with its EC2 plugin: > > > > > https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Plugin . > > These > > > > > would > > > > > be launched on demand depending on how many concurrent executors > are > > > > needed > > > > > (we'd set up a 1 executor to 1 instance mapping) and reaped when > > > > inactive. > > > > > Jenkins' EC2 plugin handles those details. > > > > > > > > > > It would remain to be seen if this is better than the ASF Jenkins > > VMs, > > > > but > > > > > if the community is willing to try it, we'd be willing to set it up > > and > > > > > give out access. With EC2's IAM (http://aws.amazon.com/iam/) it's > > > > possible > > > > > to give all committers accounts for managing these resources. An > > > m1.large > > > > > has: > > > > > - 7.5 GiB memory > > > > > - 4 EC2 Compute Units (2 virtual cores with 2 EC2 Compute Units > > > each) > > > > > - 850 GB instance storage > > > > > - 64-bit platform > > > > > - I/O Performance: Moderate > > > > > > > > > > > > > > > On Tue, Mar 19, 2013 at 5:23 PM, Nick Dimiduk <ndimi...@gmail.com> > > > > wrote: > > > > > > > > > > > What, like travis-ci.org ? > > > > > > > > > > > > On Tue, Mar 19, 2013 at 8:49 AM, Andrew Purtell < > > apurt...@apache.org > > > > > > > > > > wrote: > > > > > > > > > > > > > Would the HBase dev community be open to alternate hosted > Jenkins > > > > test > > > > > > > infrastructure? > > > > > > > > > > > > > > -- > > > > > > > Best regards, > > > > > > > > > > > > > > - Andy > > > > > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - > > Piet > > > > > Hein > > > > > > > (via Tom White) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > > > > > > - Andy > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > > > Hein > > > > > (via Tom White) > > > > > > > > > > > > > > > > > > > > > -- > > > Best regards, > > > > > > - Andy > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > Hein > > > (via Tom White) > > > > > > > > > -- > Best regards, > > - Andy > > Problems worthy of attack prove their worth by hitting back. - Piet Hein > (via Tom White) >
