hbase/dev-support/create-release
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
..
hbase-rm HBASE-21935 Replace make_rc.sh with customized spark/dev/create-release 2019-06-12 07:53:49 -07:00
README.txt HBASE-23092 Make the RM tooling in dev-tools/create-release generic (#671) 2019-10-02 09:14:17 -07:00
do-release-docker.sh HBASE-23137 [create-release] Add passing of PROJECT variable for when building other than core (#701) 2019-10-08 15:12:14 -07:00
do-release.sh HBASE-23118 [RELEASE SCRIPTS] Allow creating a RC from an existing tag[RELEASE SCRIPTS] Allow creating a RC from an existing tag (#686) 2019-10-04 13:39:27 +08:00
release-build.sh HBASE-23337 Release scripts should rely on maven for deploy. (#887) 2019-12-02 06:39:24 -06:00
release-tag.sh HBASE-23092 Make the RM tooling in dev-tools/create-release generic (#671) 2019-10-02 09:14:17 -07:00
release-util.sh HBASE-23182 The create-release scripts are broken (#736) 2019-11-19 08:28:43 +08:00
vote.tmpl HBASE-23092 Make the RM tooling in dev-tools/create-release generic (#671) 2019-10-02 09:14:17 -07:00

README.txt

Entrance script is _do-release-docker.sh_. Requires a local docker;
for example, on mac os x, Docker for Desktop installed and running.

For usage, pass '-h':

 $ ./do-release-docker.sh -h

To run a build w/o invoking docker (not recommeneded!), use
_do_release.sh_. It does not take parameters. It will ask
you what commands to run with taking defaults from environment.

Before starting the RC build, run a reconciliation of what is in
JIRA with what is in the commit log. Make sure they align and that
anomalies are explained up in JIRA.

See http://hbase.apache.org/book.html#maven.release

Running a build on GCE is easy enough. Here are some notes if of use.
Create an instance. 4CPU/15G/10G disk seems to work well enough.
Once up, run the below to make your machine fit for RC building:


# Presuming debian-compatible OS
$ sudo apt-get install -y git openjdk-8-jdk maven gnupg gnupg-agent
# Install docker
$ sudo apt-get install -y \
    apt-transport-https \
    ca-certificates \
    curl \
    gnupg2 \
    software-properties-common
$ curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add -
$ sudo add-apt-repository -y \
   "deb [arch=amd64] https://download.docker.com/linux/debian \
   $(lsb_release -cs) \
   stable"
$ sudo apt-get update
$ sudo apt-get install -y docker-ce docker-ce-cli containerd.io
$ sudo usermod -a -G docker $USERID
# LOGOUT and then LOGIN again so $USERID shows as part of docker groupl
# Copy up private key for $USERID export from laptop and import on gce.
$ gpg --import stack.duboce.net.asc
$ export GPG_TTY=$(tty) # https://github.com/keybase/keybase-issues/issues/2798
$ eval $(gpg-agent --disable-scdaemon --daemon --no-grab  --allow-preset-passphrase --default-cache-ttl=86400 --max-cache-ttl=86400)
$ git clone https://github.com/apache/hbase.git
$ cd hbase
$ mkdir ~/build
$ ./dev-resources/create-release/do-release-docker.sh -d ~/build
# etc.