[jbossts-issues] [JBoss JIRA] (JBTM-1625) Retain the commit id of the app server being used for testing
Gytis Trikleris (JIRA)
jira-events at lists.jboss.org
Wed Apr 10 09:09:57 EDT 2013
[ https://issues.jboss.org/browse/JBTM-1625?focusedWorklogId=12428995&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-12428995 ]
Gytis Trikleris logged work on JBTM-1625:
-----------------------------------------
Author: Gytis Trikleris
Created on: 10/Apr/13 9:08 AM
Start Date: 10/Apr/13 9:08 AM
Worklog Time Spent: 10 minutes
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes (was: 10 minutes)
Time Spent: 10 minutes
Worklog Id: (was: 12428995)
> Retain the commit id of the app server being used for testing
> -------------------------------------------------------------
>
> Key: JBTM-1625
> URL: https://issues.jboss.org/browse/JBTM-1625
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Build System
> Reporter: Tom Jenkinson
> Assignee: Gytis Trikleris
> Priority: Critical
> Fix For: 5.0.0.M3
>
> Original Estimate: 10 minutes
> Time Spent: 10 minutes
> Remaining Estimate: 0 minutes
>
> When we rebase jboss-as we should log the commit of the rebased master branch.
> If you just add the command:
> echo This is the JBoss-AS commit
> git rev-parse upstream/master
> That will be enough as the build log will have:
> This is the JBoss-AS commit
> d56a7873e277017e56fcbfc74f814e0d2703f503
> For example.
> This is important when we have problems introduced in the AS so we can help to identify when the problem is first observed more defined way than a timestamp (which is timezoned against a failure in Newcastle and a GitHub timestamp (whenever they are)).
--
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