You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2019/06/11 22:45:00 UTC
[jira] [Updated] (HBASE-21935) Replace make_rc.sh with customized
spark/dev/create-release
[ https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-21935:
--------------------------
Attachment: HBASE-21935.master.001.patch
> Replace make_rc.sh with customized spark/dev/create-release
> -----------------------------------------------------------
>
> Key: HBASE-21935
> URL: https://issues.apache.org/jira/browse/HBASE-21935
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Labels: rm
> Attachments: HBASE-21935.branch-2.0.001.patch, HBASE-21935.branch-2.0.002.patch, HBASE-21935.branch-2.0.003.patch, HBASE-21935.branch-2.0.004.patch, HBASE-21935.branch-2.0.005.patch, HBASE-21935.branch-2.0.006.patch, HBASE-21935.branch-2.0.007.patch, HBASE-21935.branch-2.0.008.patch, HBASE-21935.branch-2.0.009.patch, HBASE-21935.branch-2.0.010.patch, HBASE-21935.branch-2.0.011.patch, HBASE-21935.branch-2.0.012.patch, HBASE-21935.branch-2.0.013.patch, HBASE-21935.branch-2.0.014.patch, HBASE-21935.branch-2.0.015.patch, HBASE-21935.branch-2.0.016.patch, HBASE-21935.branch-2.0.017.patch, HBASE-21935.branch-2.0.018.patch, HBASE-21935.branch-2.0.019.patch, HBASE-21935.branch-2.1.001.patch, HBASE-21935.branch-2.1.002.patch, HBASE-21935.branch-2.1.003.patch, HBASE-21935.branch-2.1.004.patch, HBASE-21935.branch-2.1.005.patch, HBASE-21935.branch-2.1.006.patch, HBASE-21935.branch-2.1.007.patch, HBASE-21935.master.001.patch
>
>
> The spark/dev/create-release is more comprehensive than our hokey make_rc.sh script. It codifies the bulk of the RM process from tagging, version-setting, building, signing, and pushing. It does it in a container so environment is same each time. It has a bunch of spark-specifics as is -- naturally -- but should be possible to pull it around to suit hbase RM'ing. It'd save a bunch of time and would allow us to get to a place where RM'ing is canned, evolvable, and consistent.
> I've been hacking on the tooling before the filing of this JIRA and was polluting branch-2.0 w/ tagging and reverts. Let me make a branch named for this JIRA to play with (There is a dry-run flag but it too needs work...).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)