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

Gytis Trikleris (JIRA) jira-events at lists.jboss.org
Tue Jun 25 10:52:20 EDT 2013


     [ https://issues.jboss.org/browse/JBTM-1728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gytis Trikleris updated JBTM-1728:
----------------------------------

              Status: Pull Request Sent  (was: Open)
    Git Pull Request: https://github.com/jbosstm/narayana/pull/349

    
> 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: 15 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 should use a global env variable 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 variable WILDFLY_CURRENT_VERSION and set it to "8.0.0.Alpha2-SNAPSHOT".
> Ask paul to update the sanity check job before this is done. This will blacklist the usage of hardcoded wildfly 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


More information about the jbossts-issues mailing list