Description of problem: When a jenkins builder application is created, it currently uses the gear size which was configured when the jenkins-client cartridge was added which in turn drives the filesystem size. Instead, the builder application should be created using the current filesystem size of the application it is building (but not the gear size as the additional memory should not be needed) Steps to Reproduce: 1. Create an application with jenkins enabled 2. Add additional storage to the gear 3. Make a change to the application and push it 4. Check if the builder gear also has the additional storage available. Actual results: The builder gear does not have any additional storage Expected results: The builder gear has the same additional storage as the app being built
Why is it presumed that the extra storage on the app gear is needed for building, rather than application data?
it's not presumed, but if the app needs additional storage it's at least an indicator that the build may need additional storage too (due to either the source or binary sizes), so it makes sense to ensure that storage is available during the build.
JIRA for enhancement to the java client to support the additional storage apis (prereq for this bug): https://issues.jboss.org/browse/OSJC-101
Andre Dietisheim <adietish> updated the status of jira OSJC-101 to Closed