[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466468#comment-13466468
 ] 

David Nalley commented on CLOUDSTACK-195:
-----------------------------------------

We've previously asked infra about hooks - and one-offs simply aren't something 
that is terribly compatible with having to host/maintain scores of git repos

See the history here:
http://markmail.org/message/fgrkegpy2vlv7s3b

Historically we did have a git hook that interacted with bugzilla, but when we 
moved to Jira we used the jira plugin. Given that the SVN plugin in the ASF's 
jira instance has been disabled due to the problems it creates, I doubt we'll 
be able to use it - additionally it doesn't deliver the same level of goodness 
since you have folks with scores of git repos (like cordova, and soon to be 
maven). 

I think the only way this is possible is if we write something very generic 
hook wise that any project can make use of - and then convince a TLP or two 
already using git that they want to use such a hook, and then convince/prove to 
infra that the increased load on both git-wip-us and jira are minimal, and then 
apply it en masse to all of the repos (there are currently no repo-specific git 
hooks on tyr)  (We are still a podling after all and changing a production 
piece of the ASF's infrastructure to suit our fancy seems a bit pretentious) 
                
> Need git hookin to update jira bugs when checking in.
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-195
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-195
>             Project: CloudStack
>          Issue Type: Task
>    Affects Versions: pre-4.0.0
>            Reporter: Alex Huang
>            Assignee: David Nalley
>            Priority: Minor
>             Fix For: 4.1.0
>
>
> We should be able to use the hooks from the original git.

--
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

Reply via email to