[JENKINS-21662] Parameterized Build - List Subversion tags - Use single entry results as default value when no value selected

When having automated builds on the latest svn branches (for a TEST environment - DTAP cycle) with maximum one tag (branch) shown, and no default value given, use the only available tag for builds triggered automatically (not using build with parameters jenkins UI functionality).

Update the getDefaultParameterValue method in the ListSubversionTagsParameterDefinition class.

public ParameterValue getDefaultParameterValue() {
if (StringUtils.isEmpty(this.defaultValue)) {
List tags = getTags();
if (tags.size() != 1)

else

}
return new ListSubversionTagsParameterValue(getName(), getTagsDir(), this.defaultValue);
}

When having automated builds on the latest svn branches (for a TEST environment - DTAP cycle) with maximum one tag (branch) shown, and no default value given, use the only available tag for builds triggered automatically (not using build with parameters jenkins UI functionality).

Update the getDefaultParameterValue method in the ListSubversionTagsParameterDefinition class.


public ParameterValue getDefaultParameterValue() {
	if (StringUtils.isEmpty(this.defaultValue)) {
		List<String> tags = getTags();
		if (tags.size() != 1) 
{
			return null;
		}
 else 
{
			return new ListSubversionTagsParameterValue(getName(), getTagsDir(), tags.get(0));
			}
		}
		return new ListSubversionTagsParameterValue(getName(), getTagsDir(), this.defaultValue);
	}

Start at the getDefaultParameterValue method in ListSubversionTagsParameterDefinition and inspect how getTags, defaultValue, and ListSubversionTagsParameterValue are used. Done means an unset default selects the only available tag while other tag counts retain the existing behavior.