Description of problem:
When creating a JWS applicationk the Ref Id is pre-populated with the value "1.2"
Setting this to blank will create the image with the value "1.2" in the Build Config
Version-Release number of selected component (if applicable):
OCP 3.7 and beyond
Steps to Reproduce:
1. Create JWS Application
2. Blank out the value 1.2 for the Git version
Application build will fail as it cannot find the correct Git repo version
Build Config should not have a Ref Id value
If blank does not work, "master" also seems to work as a valid value, and could be used as a default
I don't know that this is fixable. I assume you're using the JWS template which has a parameter for the git ref. In order to make the ref parameterizable, the template must define that field, which means you must provide a valid value (e.g. either 1.2 or master, in this case).
However the template could be updated have a validation rule that makes the parameter required, which would disallow providing an empty value for it.
Not sure why it's set to 1.2 if you leave it blank, unless 1.2 is the default ref for the repo. As Ben said, you can use master if that's what's desired.
OCP 3.7 did allow blank for this field in the UI.
OCP 3.8 prevents this in the UI. (the yaml can manually be set to '')
If it can't be easily defaulted to blank, I vote for defaulting the field in 'master'.
Not forcing users to update this field when creating a JWS application makes the experience for new customers trying out the technology much better. I've had a few customers express frustration when rolling this out to new development teams and they're getting stuck at this point until they know to change this value.
Bugzilla is not used.
For JWS related issues (Tomcat core libraries), use:
For Spring related issues, use:
QA Contact for JWS on OpenShift Container Platform is: "Stanislav Kaleta" <firstname.lastname@example.org>
The demo application designed to work with the current image is on the 1.2 branch. master branch is reserved for active development, where changes may introduce incompatibilities.
Are you saying that the dev's don't know to change the git reference to what they actually need? This is pretty basic stuff, e.g. building off a release tag. I think this should be resolved WONT FIX.
IIRC, s2i + JWS is tracked on: https://issues.jboss.org/projects/CLOUD