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=cloudstack.git;h=7260e8d
This is more concise and easier to look at than the Hudson list. On Wed, Aug 27, 2014 at 10:48 AM, Karthik Kambatla <ka...@cloudera.com> wrote: > 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 <ka...@cloudera.com> > wrote: > >> 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 1:40 AM, Karthik Kambatla <ka...@cloudera.com> >> 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 build automations that folks >>> have. >>> >>> Another follow-up item: email and JIRA integration >>> >>> >>> On Wed, Aug 27, 2014 at 1:33 AM, Karthik Kambatla <ka...@cloudera.com> >>> wrote: >>> >>>> 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 and tags. >>>> 3. Even if you are experienced with git, take a look at >>>> https://wiki.apache.org/hadoop/HowToCommitWithGit . Particularly, >>>> let us avoid merge commits. >>>> >>>> Follow-up items: >>>> >>>> 1. Update rest of the wiki documentation >>>> 2. Update precommit Jenkins jobs and get HADOOP-11001 committed >>>> (reviews appreciated). Until this is done, the precommit jobs will run >>>> against our old svn repo. >>>> 3. git mirrors etc. to use the new repo instead of the old svn >>>> repo. >>>> >>>> Thanks again for your cooperation through the migration process. Please >>>> reach out to me (or the list) if you find anything missing or have >>>> suggestions. >>>> >>>> Cheers! >>>> Karthik >>>> >>>> >>> >> >
