[
https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-13673:
------------------------------------
Need max value for tests. Because at some point min won't be the same as max, and we
test w/ max while building w/ min.
Having a select box for the version doesn't provide any more value than setting it as
a hardcoded value in the job config. The top listed option is always selected when the
build runs on schedule or when upstream change fires it.
Why would you want to build one project w/ 4.30.5.Alpha and another with
4.30.5.Alpha2-SNAPSHOT ? That would just cause confusion and force you to have to READ the
logs to know what was used. IMHO it's better if all jobs for a given stream use the
same TP for building (and a different one for testing).
Besides, anyone who wants to edit the job to run once w/ a different TP can do so from the
configure menu.
jenkins jobs for components and aggregates should set overrides for
TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use
the correct TP regardless of their root pom's included parent pom version
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-13673
URL:
https://issues.jboss.org/browse/JBIDE-13673
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 4.1.0.Alpha2
jenkins jobs for components and aggregates should set overrides for
TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use
the correct TP regardless of their root pom's included parent pom version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira