hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Misty Stanley-Jones <mstanleyjo...@cloudera.com>
Subject Fwd: Successful: HBase Generate Website
Date Tue, 08 Dec 2015 05:41:32 GMT
You may notice that the instructions in this email have changed slightly.
We now have a second repository,
https://git-wip-us.apache.org/repos/asf/hbase-site.git, with a single
branch, asf-site. The Jenkins job now checks out the hbase repo as normal,
then runs mvn clean site site:stage. Next, it checks out the hbase-site
repo, removes automatically generated content, replaces that content with
the newly-built content from the hbase build, and creates a patch.

The eventual goal is to be able to have Jenkins push the updated site and
docs for us. Apache Infra are working on this last step, but until they get
it working, follow the instructions in these Jenkins emails to update the

Anyone who is an Apache committer can examine the Jenkins job:

Thanks for your patience!

---------- Forwarded message ----------
From: Apache Jenkins Server <jenkins@builds.apache.org>
Date: Mon, Dec 7, 2015 at 8:48 PM
Subject: Successful: HBase Generate Website
To: dev@hbase.apache.org, misty@apache.org

Build status: Successful

If successful, the website and docs have been generated. If failed, skip to
the bottom of this email.

Use the following commands to download the patch and apply it to a clean
branch based on origin/asf-site. If you prefer to keep the hbase-site repo
around permanently, you can skip the clone step.

  git clone https://git-wip-us.apache.org/repos/asf/hbase-site.git
  cd hbase-site
  wget -O-
| funzip > 1f999c1e2bba62fda0fb426a168afa338b31c251.patch
  git fetch
  git checkout -b asf-site-1f999c1e2bba62fda0fb426a168afa338b31c251
  git am 1f999c1e2bba62fda0fb426a168afa338b31c251.patch

At this point, you can preview the changes by opening index.html or any of
the other HTML pages in your local
asf-site-1f999c1e2bba62fda0fb426a168afa338b31c251 branch, and you can
review the differences by running:

  git diff origin/asf-site

When you are satisfied, publish your changes to origin/asf-site using this

  git push origin asf-site-1f999c1e2bba62fda0fb426a168afa338b31c251:asf-site

Changes take a couple of minutes to be propagated. You can then remove your
asf-site-1f999c1e2bba62fda0fb426a168afa338b31c251 branch:

  git checkout asf-site && git branch -d

If failed, see

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message