Bug 1063451 - [RFE]Jenkins builders do not use filesystem size from application
Summary: [RFE]Jenkins builders do not use filesystem size from application
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Image
Version: 2.x
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Ben Parees
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-10 18:44 UTC by Ben Parees
Modified: 2016-02-26 21:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-26 21:03:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSJC-101 0 Minor Closed Support Retrieving and Configuring Gear/Cartridge additional storage 2016-02-26 21:03:07 UTC

Description Ben Parees 2014-02-10 18:44:19 UTC
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

Comment 1 gideon 2014-02-12 18:54:30 UTC
Why is it presumed that the extra storage on the app gear is needed for building, rather than application data?

Comment 2 Ben Parees 2014-02-12 19:28:23 UTC
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.

Comment 3 Ben Parees 2014-03-11 18:23:07 UTC
JIRA for enhancement to the java client to support the additional storage apis (prereq for this bug):
https://issues.jboss.org/browse/OSJC-101

Comment 4 JBoss JIRA Server 2014-10-15 16:23:36 UTC
Andre Dietisheim <adietish> updated the status of jira OSJC-101 to Closed


Note You need to log in before you can comment on or make changes to this bug.