Hi Gordon,
You right that usualy, the short SHA1 id of the commit could be considerated
as unique, the point is elsewhere, I explain, a commit in Git unlike Svn
doesn't identify by force a bugfix or a new feature described in a JIRA
ticket, it can be a set of commits (so called a changeset), so, that's this
changeset that has to be linked to the JIRA ticket, that's where the FishEye
JIRA plugin comes in action, it tracks the Commits until their message
contains the Issue ID and show them up in the source tab of the JIRA isuue.
Am I clear ?
-Fred
-----Message d'origine-----
From: Gordon Smith
Sent: Monday, March 18, 2013 6:16 PM
To: dev@flex.apache.org
Subject: RE: Git and revision numbers
what can we put in JIRA to show exactly what changes that have occurred
I read that the first 7 characters of the 40-character SHA-1 hash for a
commit are typically used to identify the commit, because they are usually
enough to distinguish it. So we should use these 7 characters as a build
number.
- Gordon
-----Original Message-----
From: Justin Mclean [mailto:jus...@classsoftware.com]
Sent: Monday, March 18, 2013 12:58 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Hi,
You can check writing the JIRA ticket id in the commit message(s), push
it/them , then go to JIRA, in the source tab, you should see all the
modified files (if this feature is not broken again).
As far as I know this is not a feature we have - so what can we put in JIRA
to show exactly what changes that have occurred.
Justin
