[jira] [Created] (HBASE-19041) Precommit job that lets contributors know if their patch can be cleanly backported to targetted branches

["Sean Busbey (JIRA)" <ji...@apache.org>]

Sean Busbey created HBASE-19041:
-----------------------------------

             Summary: Precommit job that lets contributors know if their patch can be cleanly backported to targetted branches
                 Key: HBASE-19041
                 URL: https://issues.apache.org/jira/browse/HBASE-19041
             Project: HBase
          Issue Type: New Feature
          Components: test
            Reporter: Sean Busbey
            Priority: Minor


I'd like a precommit job that can comment on a jira to let contributors know when they'll need to provide a branch-specific patch. For example, when the fixVersion is set to 1.2+ and the master patch can't be cherry-picked to 1.3, we'd have a comment like:

{quote}
The provided patch 'HBASE-12345.0.patch' cleanly backports from 'master' to 'branch-2', and 'branch-1'.

The provided patch 'HBASE-12345.0.patch' fails to backport to 'branch-1.3' with a failure to cherry-pick. Details can be found at http://builds.a.o/job/HBase-Some-Job/1234/artifacts/backport-1.3-report.log.

Contributor, you will likely be asked to provide a 'branch-1.3' specific version of your patch. Most likely you will need to locally use these commands (presuming your original patch is on a feature branch named after this jira, 'HBASE-12345') and resolve any conflicts:

{code}
$> git checkout origin/branch-1.3 -b HBASE-12345-branch-1.3
$> git cherry-pick HBASE-12345
... conflict should be here ...
{code}

Once you have resolved the conflict, please generate a patch and attach it here, following the branch-specific naming guidelines.

{code}
$> git format-patch --stdout origin/branch-1.3 > /some/path/to/patches/HBASE-12345-branch-1.3.v0.patch
{code}
{quote}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)