The problem seems to be the Maven snapshot repo it's been keeping around forever - I'm trying to drill down further, but I can tell at this point that 40gb or so is being used by the various Maven repos in Forge. I emailed demobox, and am trying to see what I can do about this in the near term.
A. On Thu, Jul 11, 2013 at 11:42 AM, Matt Stephenson <[email protected]>wrote: > The javadoc is big, are we doing that in buildhive now? > > > On Thu, Jul 11, 2013 at 11:41 AM, Everett Toews < > [email protected] > > wrote: > > > I just saw this error message in CloudBees. > > > > "Build execution is suspended due to the following reason(s): > > > > Your total DEV@Cloud disk usage is over your subscription's quota. Your > > subscription 'enterprise-monthly' allows 50 GB, but you are using 51213 > MB > > across all services (Forge and Jenkins). To fix this, you can either > > upgrade your subscription or delete some data in your Forge repositories, > > Jenkins workspaces or build artifacts." > > > > What's taking up the lion's share of the build artifacts? > > > > It's not the jclouds-site builds as they're only 36 MB per build with a > > max of 10 builds to keep. > > > > Everett >
