Commit Graph

9 Commits

Author SHA1 Message Date
Sean Busbey 97e0107000
HBASE-23337 Release scripts should rely on maven for deploy. (#887)
- switch to nexus-staging-maven-plugin for asf-release
- refactor release-build to use mvn deploy and its output.
- cleaned up some tabs in the root pom

Signed-off-by: stack <stack@apache.org>
2019-12-02 06:39:24 -06:00
Duo Zhang 4b99816dd6
HBASE-23182 The create-release scripts are broken (#736)
Signed-off-by: stack <stack@apache.org>
Signed-off-by: Bharath Vissapragada <bharathv@apache.org>
2019-11-19 08:28:43 +08:00
Michael Stack 57439e5bf5
HBASE-23137 [create-release] Add passing of PROJECT variable for when building other than core (#701) 2019-10-08 15:12:14 -07:00
Frederick Ayala 95c9911a9c HBASE-23031 Upgrade Yetus version in RM scripts (#692)
Signed-off-by: Peter Somogyi <psomogyi@apache.org>
2019-10-06 11:24:35 +02:00
stack f69e7705e0 HBASE-23121 create-release is not pushing artifacts to repository.a.o 2019-10-04 15:32:17 -07:00
Duo Zhang f08a310ed9
HBASE-23118 [RELEASE SCRIPTS] Allow creating a RC from an existing tag[RELEASE SCRIPTS] Allow creating a RC from an existing tag (#686)
Signed-off-by: stack <stack@apache.org>
2019-10-04 13:39:27 +08:00
Michael Stack 7ee6d59ef8
HBASE-23092 Make the RM tooling in dev-tools/create-release generic (#671)
Make the scripts generic. Adds an option that allows you specify
'project'. Defaults to 'hbase' for core. Pass 'hbase-thirdparty'
or 'hbase-operator-tools' etc.

This commit includes a bunch of bugfixes and miscellaneous
that came of trying to use the scripts making RCs.

Signed-off-by: Peter Somogyi <psomogyi@apache.org>
2019-10-02 09:14:17 -07:00
stack 53db390f60 HBASE-22854 Remove +x shell spew from do-release-*.sh create-release scripts 2019-08-14 10:05:41 -07:00
stack 8745d5e7e8 HBASE-21935 Replace make_rc.sh with customized spark/dev/create-release
These scripts came originally from spark [1]. They were then
modified to suit hbase context. Supercedes the old
../make_rc.sh script because what is here is more comprehensive
doing more steps of the RM process as well as running in a
container so the RM build environment can be a constant.

It:
 * Tags release
 * Updates RELEASENOTES.md and CHANGES.md.
 * Sets version to the release version
 * Sets version to next SNAPSHOT version.
 * Builds, signs, and hashes all artifacts.
 * Generates the API report.
 * Pushes release tgzs to the dev dir in a apache dist.
 * Pushes to repository.apache.org staging.
 * Generates a vote email with filled-in fields.

The entry point is the do-release-docker.sh script. Pass -h to
see available options. For example, running below will do all
steps above using the 'rm' dir under Downloads as workspace:

 $ ./do-release-docker.sh  -d ~/Downloads/rm

1. https://github.com/apache/spark/tree/master/dev/create-release

Signed-off-by: Peter Somogyi <psomogyi@cloudera.com>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
2019-06-12 07:53:49 -07:00