svngit2jira would write a message like this -
https://issues.apache.org/jira/browse/CLOUDSTACK-1638?focusedCommentId=13714929&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13714929
with a link to the commit like this -
https://git-wip-us.apache.org/repos/asf?p=clouds
It appears the comments from Hudson on our JIRAs (post commits) are not
setup by the INFRA team. Do we use any other scripts for this? If yes, do
we want to fix those scripts or use svngit2jira?
On Wed, Aug 27, 2014 at 10:18 AM, Karthik Kambatla
wrote:
> The emails for commits apparently all go
The emails for commits apparently all go to common-commits@, irrespective
of the project. Apparently, the git filtering is not as good as svn
filtering. Daniel offered to look into alternatives this coming weekend.
I filed INFRA-8250 to restore updates to JIRA on commits.
On Wed, Aug 27, 2014 at
Committed YARN-2035 successfully via git. Email notification seems to work
already.
On Wed, Aug 27, 2014 at 1:40 AM, Karthik Kambatla
wrote:
> Oh.. a couple more things.
>
> The git commit hashes have changed and are different from what we had on
> our github. This might interfere with any buil
Oh.. a couple more things.
The git commit hashes have changed and are different from what we had on
our github. This might interfere with any build automations that folks
have.
Another follow-up item: email and JIRA integration
On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla
wrote:
> Hi fol
Hi folks,
I am very excited to let you know that the git repo is now writable. I
committed a few changes (CHANGES.txt fixes and branching for 2.5.1) and
everything looks good.
Current status:
1. All branches have the same names, including trunk.
2. Force push is disabled on trunk, branch-2
