Please see if we can use this hook for ASF repo. This hook will translate the GIT commit information to JIRA automatically. We have already implemented the same for Citrix repo and it is working well as of now.
Thanks, Pradeep.S From: Nitin Mehta Sent: Thursday, November 01, 2012 8:25 PM To: Pradeep Soundararajan Cc: Koushik Das; Frank Zhang; Abhinandan Prateek; Ram Chinta; Sudha Ponnaganti; Ram Ganesh; #Cloud - Engineering Subject: Re: Enabled GIT-JIRA connector Superb. I think this has been through enough rounds of discussion so I am taking the liberty of opening it to the entire engineering :) to follow for git commits in future ? I think you should also try and do this for ASF repository as well so start the discussion. Thanks, -Nitin On 01-Nov-2012, at 4:33 PM, Pradeep Soundararajan wrote: Hi Nitin, Right now the respective branch name is getting printed on the JIRA. And also, you can do the git commit without "refs #". Right now it will accept for an example either "git commit -m "anytext CS-16317 anytext" or "git commit -m "CS-16317 anytext" I will try to implement other feedbacks during my next phase. That will take sometime ☺. Thanks, Pradeep.S -----Original Message----- From: Nitin Mehta Sent: Tuesday, October 30, 2012 6:49 PM To: Pradeep Soundararajan; Koushik Das Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: RE: Enabled GIT-JIRA connector Hi Pradeep, Thanks for effort on this. Certain things that you might want to look into 1. Put in the branch name in the Jira ticket - remember this is extremely important if the user is merging it to several branches. 2. Strip out 'refs #' in the message. I do not think that should be required. 3. In the next phase you should add functionality for updating multiple bugs in one go as well. something like CS-16317, 16318 - commit msg Thanks, -Nitin ________________________________________ From: Pradeep Soundararajan Sent: Tuesday, October 30, 2012 6:29 PM To: Koushik Das; Nitin Mehta Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: RE: Enabled GIT-JIRA connector Thanks Koushik for trying ☺ Yes, I have a plan to do that in the next phase. Let me try to complete as earliest as possible… Thanks, Pradeep.S From: Koushik Das Sent: Tuesday, October 30, 2012 4:51 PM To: Pradeep Soundararajan; Nitin Mehta Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: RE: Enabled GIT-JIRA connector Thanks Pradeep for this tool. I tried it and the bug got updated appropriately. I think it might be useful to also mark the issue as ‘Resolved’. Comments? -Koushik From: Pradeep Soundararajan Sent: Tuesday, October 30, 2012 11:39 AM To: Nitin Mehta Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: RE: Enabled GIT-JIRA connector Right now it is not necessary to perform the below steps by storing the git configurations in the global .gitconfig. I have created a common account which will translate the GIT commit info to JIRA automatically when it finds a new commit. Please make sure the ticket should not be a private ticket. GIT commit message format: “refs #CS-16317 xxxxx ticket description xxxxx” The commit message should have the mandatory info “refs #CS-16317”. The hook will try to look for this info before translating the message to a JIRA. Please take care of this. Let me know if you see any issues… Thanks, Pradeep.S From: Pradeep Soundararajan Sent: Monday, October 08, 2012 11:08 PM To: Nitin Mehta Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: RE: Enabled GIT-JIRA connector Thanks Nitin for the comments☺ Please find my comment inline… From: Nitin Mehta Sent: Monday, October 08, 2012 9:56 PM To: Pradeep Soundararajan Cc: Frank Zhang; Abhinandan Prateek; #Cloud-CloudStack-India; Ram Chinta; Sudha Ponnaganti; Ram Ganesh Subject: Re: Enabled GIT-JIRA connector Great work Pradeep. Thanks. But I think there is still some more work required before everyone adopts it. I think there two issues which will make this procedure unviable. git config --global jira.url "http://bugs.cloudstack.org/"; git config --global jira.user <jira-user-name> git config --global jira.password <jira-password> * These settings would work only for 1 user as it gets overwritten every time a user would log in and change it in the machine. * Also we would be exposing the password in clear text which is not acceptable to me. Pradeep: Since each and every one are going to log-in with their credentials (one time activity), their global .gitconfig will get created on their home directory of git.cloud.com<http://git.cloud.com>. You can still protect your home directory with “700” so that others cannot not view your password. There is way where we can encrypt the password but that would require manual intervention for each push. Currently, that is working fine only in my test environment but not in the production env. Hence, I have followed the above approach. I will try to make it in my 2nd phase. Before everyone takes this path I suggest you to please try out the entire procedure with a couple of developers by creating dummy bugs ? Also can we keep the grammar consistent with what we had earlier and also add the feature to automatically update the ticket status as well ? Pradeep: I am unable to trace the old grammar technics. Anyway, I am thinking to incorporate the additional feature which will update the ticket automatically during my 2nd phase. Thanks, -Nitin On 08-Oct-2012, at 9:22 PM, Pradeep Soundararajan wrote: Apologize for the delay… I have enabled the GIT-JIRA connector. Right now the commit info is getting updated properly to the respective JIRA ID (CS-####). Requirement as follows: 1. Login to git.cloud.com<http://git.cloud.com><http://git.cloud.com> with your privilege 2. Execute the below: git config --global jira.url "http://bugs.cloudstack.org/"; git config --global jira.user <jira-user-name> git config --global jira.password <jira-password> 1. Log out git.cloud.com<http://git.cloud.com><http://git.cloud.com> 2. git commit example: “git commit -m "refs #CS-16317 Dummy ticket". Always, the comments should be amended with “refs #CS-xxxxx description”. Please try and let me know if you see any more issues. Thanks, Pradeep.S -----Original Message----- From: Pradeep Soundararajan Sent: Tuesday, September 18, 2012 5:04 PM To: Nitin Mehta; Frank Zhang; Abhinandan Prateek Cc: Ram Chinta; Sudha Ponnaganti Subject: RE: git checkin grammar for updating Jira automatically Hi Nitin, I am busy with ASF bug fixes and other build related stuff. Right now I am not spending much time on my private tickets. Anyway, I have got to know the fix for this but it is in testing phase. It is really working well in my test environment. I have to put into the production once my testing is done. Let me see if I can fix that one tomorrow. Thanks, Pradeep.S -----Original Message----- From: Nitin Mehta Sent: Tuesday, September 18, 2012 5:00 PM To: Frank Zhang; Pradeep Soundararajan; Abhinandan Prateek Subject: RE: git checkin grammar for updating Jira automatically Pradeep - Were you able to make progress on this ? With the number of releases we have this would be highly beneficial -----Original Message----- From: Frank Zhang Sent: Friday, September 07, 2012 11:10 PM To: Pradeep Soundararajan; Nitin Mehta; Abhinandan Prateek Subject: RE: git checkin grammar for updating Jira automatically I don't know about jira, you may investigate if there any jira plugin doing this The magic before was in update script in git hook, it simply does: python /usr/bin/updatebz.py "$1" "$2" "$3" exit 0 > -----Original Message----- > From: Pradeep Soundararajan > Sent: Friday, September 07, 2012 3:37 AM > To: Nitin Mehta; Abhinandan Prateek > Cc: Frank Zhang > Subject: RE: git checkin grammar for updating Jira automatically > > Nitin, I am not seeing any hook written under cloudstack-oss for this > right now ? > > Any way let's wait for his feedback. > > > -----Original Message----- > From: Nitin Mehta > Sent: Friday, September 07, 2012 3:53 PM > To: Pradeep Soundararajan; Abhinandan Prateek > Cc: Frank Zhang > Subject: RE: git checkin grammar for updating Jira automatically > > +Frank. > > Pradeep - I don’t think anyone would know here. Frank should be able > to tell how it was implemented. I am guessing a simple hook at the git > server for any incoming commits. > > -----Original Message----- > From: Pradeep Soundararajan > Sent: Friday, September 07, 2012 3:50 PM > To: Nitin Mehta; Abhinandan Prateek > Subject: RE: git checkin grammar for updating Jira automatically > > +Abhi > > > -----Original Message----- > From: Pradeep Soundararajan > Sent: Friday, September 07, 2012 3:07 PM > To: Nitin Mehta > Subject: FW: git checkin grammar for updating Jira automatically > > Hi Nitin, > > Could you please let me know where I can find the BZ code base? Was it > controlled by Subversion? > > Thanks, > Pradeep.S > > > -----Original Message----- > From: Pradeep Soundararajan > Sent: Tuesday, September 04, 2012 7:02 PM > To: David Nalley > Cc: Frank Zhang > Subject: RE: git checkin grammar for updating Jira automatically > > Thanks David. Could you please point me to that BZ code base location? > > > -----Original Message----- > From: David Nalley > [mailto:david.nal...@citrix.com]<mailto:[mailto:david.nal...@citrix.com]><mailto:[mailto:david.nal...@citrix.co > m]> > Sent: Tuesday, September 04, 2012 5:52 PM > To: Pradeep Soundararajan > Cc: Frank Zhang > Subject: Re: git checkin grammar for updating Jira automatically > > No, nothing as fancy as fisheye or rally. Just the Jira git plugin. > Several comments though. > While the git plugin will annotate the ticket itself, it won't > automagically close/resolve the ticket. You could also look at the > source of the githook for BZ - and modify it to do similar things for jira. > > --David > > > On 09/04/2012 05:16 AM, Pradeep Soundararajan wrote: > > Hello David/Frank, > > > > > > > > Have we ever used any connector to perform this earlier for Citrix? > > > > > > > > I feel, now it has been broken down. Please provide me the hint is > > that a fisheye or rally or something, where it is installed? > > > > > > > > Thanks, > > > > Pradeep.S > > > > > > > > *From:*Pradeep Soundararajan > > *Sent:* Tuesday, September 04, 2012 10:28 AM > > *To:* Abhinandan Prateek; Nitin Mehta > > *Cc:* Ram Chinta; Sudha Ponnaganti; Frank Zhang > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > Hi Abhi/Nitin, > > > > > > > > Do you remember have we ever used any Connector or something (Rally > > for > > example) which will translate the commit to JIRA bug-id. > > > > > > > > There should be an connector which is responsible for any grammar check. > > I feel, without that the defect-id would not get translated to JIRA. > > Did we have anything like that earlier? > > > > > > > > Thanks, > > > > Pradeep.S > > > > > > > > *From:*Pradeep Soundararajan > > *Sent:* Tuesday, September 04, 2012 9:38 AM > > *To:* Ram Chinta; Abhinandan Prateek; Nitin Mehta; #Cloud - > > Engineering > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > Sure, I am going to look at it by today. > > > > > > > > Thanks, > > > > Pradeep.S > > > > > > > > *From:*Ram Chinta > > *Sent:* Tuesday, September 04, 2012 9:36 AM > > *To:* Abhinandan Prateek; Pradeep Soundararajan; Nitin Mehta; #Cloud > > - Engineering > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > Pradeep – Can you fix this for Citrix git and jira, and figure out > > what might have broken it. This used to work. > > > > > > > > *From:*Abhinandan Prateek > > *Sent:* Monday, September 03, 2012 4:28 PM > > *To:* Pradeep Soundararajan; Ram Chinta; Nitin Mehta; #Cloud - > > Engineering > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > When a git commit is make with a bug id, the Jira bug with that id > > should be updated with the git commit id and the branch. > > > > This will link the Jira with git commits. > > > > > > > > -abhi > > > > > > > > *From:*Pradeep Soundararajan > > *Sent:* Monday, September 03, 2012 4:08 PM > > *To:* Ram Chinta; Nitin Mehta; #Cloud - Engineering > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > Sure, let me understand the real issue. > > > > > > > > Are we looking for something to validate the GIT commit message or > > auto update the JIRA tool from Open/assign state to resolve status > > based on the commit message (CS #) or do I need to know other than this? > > > > > > > > Thanks, > > > > Pradeep.S > > > > > > > > *From:*Ram Chinta > > *Sent:* Monday, September 03, 2012 1:50 PM > > *To:* Nitin Mehta; #Cloud - Engineering > > *Cc:* Pradeep Soundararajan > > *Subject:* RE: git checkin grammar for updating Jira automatically > > > > > > > > Pradeep – Can you look into this? > > > > > > > > *From:*Nitin Mehta > > *Sent:* Monday, September 03, 2012 12:26 PM > > *To:* #Cloud - Engineering > > *Subject:* git checkin grammar for updating Jira automatically > > > > > > > > We used to have a grammar > > <http://intranet.lab.vmops.com/engineering/101/developer- > information/s > > vn-checkins/?searchterm=bugzilla> for the git checkin messages that > > used to automatically get updated on bz. This used to update the bz > > automatically for all the branches and also resolved the bugs. > > > > Example commit message. > > > > bug 5873: Checking if scmbug works > > > > status 5873: resolved fixed > > > > > > > > I think we tried to adopt to a new grammar for Jira but it's not > > working for a number of devs. It’s important to resolve this as we > > are losing all the branches(particularly ASF master) > > > > that our checkin goes to and QA/devs are finding it difficult to > > track the different commit messages. > > > > > > > > Thanks, > > > > -Nitin > >
