Details
-
Task
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
Reviewed
-
Description
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...).
Attachments
Attachments
Issue Links
1.
|
Point make_rc.sh at ./create-release/do-release-docker.sh instead | Resolved | Michael Stack | |
2.
|
Update subtask to reference create-release/do-release-docker.sh script | Resolved | Unassigned | |
3.
|
Auto insert release changes and releasenotes in release scripts | Resolved | Unassigned | |
4.
|
Auto-generate api report in release script | Resolved | Unassigned | |
5.
|
[DEBUG] Exit if git returns empty revision! | Resolved | Michael Stack | |
6.
|
RESTApiClusterManager.java:[250,48] cannot find symbol in hbase-it | Resolved | Unassigned | |
7.
|
Add markers to CHANGES.md and RELEASENOTES.md | Resolved | Michael Stack | |
8.
|
Try running create-release against branch-1 | Resolved | Michael Stack |