Bug 1015875

Summary: Jenkins server accepts invalid gear sizes
Product: OpenShift Online Reporter: gideon
Component: ContainersAssignee: Jhon Honce <jhonce>
Status: CLOSED UPSTREAM QA Contact: libra bugs <libra-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.xCC: dmace, gideon
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-07 18:41:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description gideon 2013-10-06 12:59:35 UTC 
Steps to Reproduce:
1. Create an app from the Jenkins server cartridge
2. Create a new Jenkins job
3. Set the Builder Size to a nonsensical value
4. Save the configuration

Actual results:

The configuration is saved with the invalid value.

Expected results:

The user is alerted to the invalid value, and the configuration is not saved.
Ideally, the user will only be allowed to select a builder size from a fixed list of valid sizes.
Comment 1 Dan Mace 2013-10-07 18:41:25 UTC 
The long term fix for this is to remove the field entirely, which is covered in the backlog:

https://trello.com/c/asBkl7Uo/123-the-jenkins-cloud-plugin-should-use-the-originating-app-rather-than-just-builder-type-java-future

Closing this as upstream. Thanks.
Comment 2 gideon 2013-10-09 11:25:31 UTC 
Will this allow for the possibility that an app needs a medium gear to compile but can run happily on a small gear, or vice versa?