Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id AAA7A200AF6 for ; Fri, 27 May 2016 09:38:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A914A160A12; Fri, 27 May 2016 07:38:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F280C16099F for ; Fri, 27 May 2016 09:38:14 +0200 (CEST) Received: (qmail 64608 invoked by uid 500); 27 May 2016 07:38:13 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 64287 invoked by uid 99); 27 May 2016 07:38:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 May 2016 07:38:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1AC422C1F64 for ; Fri, 27 May 2016 07:38:13 +0000 (UTC) Date: Fri, 27 May 2016 07:38:13 +0000 (UTC) From: "Appy (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HBASE-15892) Single command line to make patch, upload it to jira, and update review board MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 27 May 2016 07:38:15 -0000 [ https://issues.apache.org/jira/browse/HBASE-15892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Appy updated HBASE-15892: ------------------------- Description: Adds dev-support/submit-patch.py The script builds a new patch (using specified branch/tracking branch as base branch), uploads it to jira, and updates diff of the review on ReviewBoard. Remote links in the jira are used to figure out if a review request already exists. If no review request is present, then creates a new one and populates all required fields using jira summary, patch description, etc. *Authentication* Since attaching patches & changes links on JIRA and creating/changing review request on ReviewBoard requires a logged in user, the script will prompt you for username and password. To avoid the hassle every time, I'd suggest setting up ~/.apache-creds with the login details and encrypt it as explained in scripts help message footer. > Single command line to make patch, upload it to jira, and update review board > ----------------------------------------------------------------------------- > > Key: HBASE-15892 > URL: https://issues.apache.org/jira/browse/HBASE-15892 > Project: HBase > Issue Type: New Feature > Reporter: Appy > Assignee: Appy > Priority: Trivial > Fix For: 2.0.0 > > Attachments: HBASE-15892_branch-1_v1.patch, HBASE-15892_master_v1.patch, HBASE-15892_master_v2.patch, HBASE-15892_master_v3.patch > > > Adds dev-support/submit-patch.py > The script builds a new patch (using specified branch/tracking branch as base branch), uploads it to jira, and updates diff of the review on ReviewBoard. > Remote links in the jira are used to figure out if a review request already exists. If no review request is present, then creates a new one and populates all required fields using jira summary, patch description, etc. > *Authentication* > Since attaching patches & changes links on JIRA and creating/changing review request on ReviewBoard requires a logged in user, the script will prompt you for username and password. To avoid the hassle every time, I'd suggest setting up ~/.apache-creds with the login details and encrypt it as explained in scripts help message footer. -- This message was sent by Atlassian JIRA (v6.3.4#6332)