[jbossts-issues] [JBoss JIRA] (JBTM-1728) Use a global environment variable in CI for version numbers of Narayana and WildFly

[Gytis Trikleris (JIRA)]

     [ https://issues.jboss.org/browse/JBTM-1728?focusedWorklogId=12429426&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12429426 ]

Gytis Trikleris logged work on JBTM-1728:
-----------------------------------------

                Author: Gytis Trikleris
            Created on: 28/Jun/13 8:37 AM
            Start Date: 28/Jun/13 8:37 AM
    Worklog Time Spent: 40 minutes 

Issue Time Tracking
-------------------

    Time Spent: 55 minutes  (was: 15 minutes)
    Worklog Id:     (was: 12429426)


> Use a global environment variable in CI for version numbers of Narayana and WildFly
> -----------------------------------------------------------------------------------
>
>                 Key: JBTM-1728
>                 URL: https://issues.jboss.org/browse/JBTM-1728
>             Project: JBoss Transaction Manager
>          Issue Type: Enhancement
>      Security Level: Public(Everyone can see) 
>          Components: Build System, Testing
>            Reporter: Paul Robinson
>            Assignee: Gytis Trikleris
>             Fix For: 5.0.0.M4
>
>   Original Estimate: 2 hours
>          Time Spent: 55 minutes
>  Remaining Estimate: 0 minutes
>
> We have "8.0.0.Alpha2-SNAPSHOT" scattered over many jobs. This is a pain to change every time we have a new release of Wildfly. We also have the same issue with jboss-as-7.2.0.Final.
> We should use global env variables instead. See the following for how to do it. Notice that I have already added one for Narayana.
> http://172.17.131.2/configure
> Call the variables:
> WILDFLY_MASTER_VERSION=8.0.0.Alpha2-SNAPSHOT
> JBOSS_7_2_VERSION=7.2.0.Final
> Ask paul to update the sanity check job before this is done. This will blacklist the usage of hardcoded wildfly/jboss version numbers. It will make it a lot easier to find all the places it is used.

--
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