[
https://issues.apache.org/jira/browse/HBASE-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778540#comment-16778540
]
Sean Busbey edited comment on HBASE-21935 at 2/26/19 8:15 PM:
--------------------------------------------------------------
bq. I think us on branch-2 do similar to your practice making a JIRA and then
sub-jiras to do each substep (should be less of this w/ this script in place –
TODO: write it up).
This means there'll be an open JIRA with the relevant fix version, no?
bq. What is nightly doing to help out RMing?
Some time ago I set up a nightly test that followed the steps in the book,
because one time when I went to try to make an RC the steps failed. (I don't
remember specifics of the failure any more).
here is the start of the test definition on current master:
[dev-support/Jenkinsfile line
495|https://github.com/apache/hbase/blob/7377fcd29bf45208214973547facf4853620fba8/dev-support/Jenkinsfile#L495]
I only really pay attention to how it's doing for branch-1.2, so I have no idea
if it's currently useful for branches-2.
was (Author: busbey):
bq. I think us on branch-2 do similar to your practice making a JIRA and then
sub-jiras to do each substep (should be less of this w/ this script in place –
TODO: write it up).
This means there'll be an open JIRA with the relevant fix version, no?
bq. What is nightly doing to help out RMing?
Some time ago I set up a nightly test that followed the steps in the book,
because one time when I went to try to make an RC the steps failed. (I don't
remember specifics of the failure any more).
here is the starts of the test definition:
https://github.com/apache/hbase/blob/master/dev-support/Jenkinsfile#L495
I only really pay attention to how it's doing for branch-1.2, so I have no idea
if it's currently useful for branches-2.
> 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: rm
> Reporter: stack
> Assignee: stack
> Priority: Minor
> Labels: rm
> Attachments: HBASE-21935.branch-2.1.001.patch,
> HBASE-21935.branch-2.1.002.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)
