1) Looking at JIRA ticket, what changes to Git were related
Time ago, Bertrand commented a JIRA ticket [1] to activate FishEye on JIRA
for the Flex project but it has been closed, sending us to Altassian but
nothing has been done on that way, so, I opened a FishEye ticket [2]
following the instructions there [3]
2) Looking at GIT log to see what JIRA issues got fixed (in order to update
release notes or when someone asks if a release contains a fix)
In order to make FishEye to track our commits, the Git log should contain
the JIRA Ticket id, a list of links to the files added to the commit will
then be shown in the JIRA issue under the source tab.
3) Determining if a release contains a particular commit/push
A way could be to have a script to parse JIRA and check what was resolved
since the last release, personaly, I never did it but I know that's
possible.
4) Monotonically increasing build numbers for version checking
Can we solve #3 and #4 by substituting YYYYMMDD as the build number?
Yes, that's maybe the way to solve #3 and #4
I saw suggestions that you name branches with the JIRA issue. I assume
that is because the branch name shows up automatically in the log when
pushed?
Otherwise it is just a convention and folks will make mistakes.
In all the middle and big companies I worked for, it was use like that by
convention, it's easier to retreive my branch if I use the JIRA Ticket ID as
I can have several open on several projects, ok, maybe not for Flex :)
Could we put a URL to the log message or even commit email in the JIRA
issue?
Until the FishEye issue is not resolved, I guess yes, and we should write
the JIRA id as well in the log of the commit, like that, when resolved,
we'll have an uniform way to see the things, it still to be determinate if
svn and git could work could be tracked by the same FishEye instance, I'll
ask them as soon they'll answer, currently, the status changed to
investigating.
-Fred
[1] https://issues.apache.org/jira/browse/INFRA-5635
[2] https://support.atlassian.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 solve.
I think there are actually several. I can think of:
1) Looking at JIRA ticket, what changes to Git were related
2) Looking at GIT log to see what JIRA issues got fixed (in order to update
release notes or when someone asks if a release contains a fix)
3) Determining if a release contains a particular commit/push
4) Monotonically increasing build numbers for version checking
It looks like folks solve #4 by counting commits to master. I guess that's
ok, but doesn't really seem that helpful. Can we solve #3 and #4 by
substituting YYYYMMDD as the build number? I think it solves #2 as well:
you can see if the log shows the JIRA issue before the date decoded from the
build number.
For #1, knowing the hash or partial hash still doesn't give you a sense for
when it happened. I suppose we could use dates here as well to at least
bracket what changes and assuming the log mentions the JIRA issue.
I saw suggestions that you name branches with the JIRA issue. I assume that
is because the branch name shows up automatically in the log when pushed?
Otherwise it is just a convention and folks will make mistakes.
Could we put a URL to the log message or even commit email in the JIRA
issue?
On 3/18/13 2:49 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:
Hi Jose,
I thought about the short sha1 too and it could work, I was thinking about
a
lightweight tag too (more readable), 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
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 Barragan
Chief Software Architect
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5. 505.
28020 Madrid.
Tel.: +34 912 94 80 80
On Mar 18, 2013, at 10:17 AM, Frédéric THOMAS <webdoubl...@hotmail.com>
wrote:
JIRA use the JIRA Fisheye plugin to link the sources with, aparently,
it's
not setup for our project, I retreived the infra ticket [1], we can then
directly deal with altassian to setup our project with fisheye.
From [2] :
Support FAQ
Can we use Fisheye to browse and search our repository?
Yes. See http://fisheye6.atlassian.com/ for some working examples. (Our
Jira Fisheye currently disabled, looking into it)
The people at Atlassian kindly provide FishEye instances of ASF projects,
upon request.
First, check with your project's PMC, and then ask Atlassian to setup a
FishEye instance for your project. (No need to keep infra the loop.)
Create a support request at Atlassian Support in the FishEye project.
Please use the "Public Hosting" component for your request.
If there is no response after a reasonable amount of time, infra has
access to set up projects on Fisheye, but consider this a last resort
option, Atlassian should be first point of contact.
Atlassian now run a local synced copy of the ASF repository, hence
requests can now be made direct without infra needing to be involved.
So, I decided to open an issue at Altassian fisheye [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 revision numbers
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 (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 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
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
