Maybe ant's BuildNumber task could be used:
http://ant.apache.org/manual/Tasks/buildnumber.html
--Dasa
On Mar 18, 2013, at 10:32 AM, Alex Harui wrote:
>
>
>
> On 3/18/13 10:16 AM, "Gordon Smith" wrote:
>
>>> what can we put in JIRA to show exactly what changes that have occurred
>>
>> I r
Oups, sorry guys I misread, I was out of subject, I thought you was talking
about the bidirectional commits/JIRA links.
-Fred
-Message d'origine-
From: Alex Harui
Sent: Monday, March 18, 2013 6:32 PM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
On 3/18/13
On 3/18/13 10:16 AM, "Gordon Smith" wrote:
>> 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
> distinguis
7;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 typica
ild 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
assian.com/browse/JST-59433
[3] https://cwiki.apache.org/INFRA/infra-faq.html
-Message d'origine-
From: Alex Harui
Sent: Monday, March 18, 2013 4:24 PM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Let's stop for a second and identify what problems we are trying to s
able), not sure though what is the best, I
> have to dig into more deeply.
>
> Thanks,
> -Fred
>
> -Message d'origine-
> From: Jose Barragan
> Sent: Monday, March 18, 2013 10:37 AM
> To: dev@flex.apache.org
> Subject: Re: Git and revision numbers
>
37 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
In my work, I use the build number of the Hudson, or occasionally the short
version of the commit SHA that I am building.
Anyway, I leave as you get the short version of the SHA, in GIT
git log -1 --pretty=format:%h
--
Jose Bar
e/INFRA-5635
> [2] https://cwiki.apache.org/INFRA/infra-faq.html
> [3] https://support.atlassian.com/browse/JST-59433
>
> -Message d'origine- From: Frédéric THOMAS
> Sent: Monday, March 18, 2013 9:29 AM
> To: dev@flex.apache.org
> Subject: Re: Git and revision
3]
-Fred
[1] https://issues.apache.org/jira/browse/INFRA-5635
[2] https://cwiki.apache.org/INFRA/infra-faq.html
[3] https://support.atlassian.com/browse/JST-59433
-Message d'origine-
From: Frédéric THOMAS
Sent: Monday, March 18, 2013 9:29 AM
To: dev@flex.apache.org
Subject: Re: Git and
Who is JIRA admin btw ? it seem the fisheye plugin is there but
misconfigured.
-Fred
-Message d'origine-
From: Frédéric THOMAS
Sent: Monday, March 18, 2013 9:19 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
That's a feature we have but maybe broken
That's a feature we have but maybe broken (we should deal with infra IMO).
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Monday, March 18, 2013 8:58 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Hi,
You can check writing the JIRA ticket id in
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 exact
2013 4:06 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Hi,
which I squash a merge time using git merge --squash -m 'new ' newFeature.
And you loose all of your local commit history then. I'm not sure if that is
ideal or not - guess it depends on how big the change is
Hi,
> which I squash a merge time using git merge --squash -m 'new ' newFeature.
And you loose all of your local commit history then. I'm not sure if that is
ideal or not - guess it depends on how big the change is but that local history
log may be useful.
Still no idea how we indicate what cha
'new
' newFeature.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Monday, March 18, 2013 3:54 AM
To: dev@flex.apache.org
Subject: Re: Git and revision numbers
Hi,
Also how do we identify which GIT check in fixed a JIRA bug? Used to be
that we just add the SVN r
Hi,
>> Also how do we identify which GIT check in fixed a JIRA bug? Used to be
>> that we just add the SVN revision checkin but now a push can result in
>> several checkins.
>
> I would say indicating the JIRA Ticket id in the commit message
In every commit message? You may make a dozen or mor
ticket but this feature didn't work with our
SVN, I don't know if we'll be luckier with GIT.
-Fred
-Message d'origine-
From: Justin Mclean
Sent: Monday, March 18, 2013 3:28 AM
To: dev@flex.apache.org
Subject: Git and revision numbers
Hi,
As far as I can see Git ha
Hi,
As far as I can see Git has no check in revision numbers. Currently the build
release process uses SVN version number I think the number is appended to the
RSLs and may be used elsewhere.
Anyone have any ideas on how to resolve this?
Also how do we identify which GIT check in fixed a JIRA
19 matches
Mail list logo
