hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <bus...@cloudera.com>
Subject Re: Successful: HBase Generate Website
Date Mon, 25 Jul 2016 16:02:38 GMT

On Sun, Jul 24, 2016 at 10:09 AM, Apache Jenkins Server
<jenkins@builds.apache.org> wrote:
> 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- https://builds.apache.org/job/hbase_generate_website/297/artifact/website.patch.zip
| funzip > bdd7782f054a4740bb63f4d9781ffe083d51e4bf.patch
>   git fetch
>   git checkout -b asf-site-bdd7782f054a4740bb63f4d9781ffe083d51e4bf origin/asf-site
>   git am --whitespace=fix bdd7782f054a4740bb63f4d9781ffe083d51e4bf.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-bdd7782f054a4740bb63f4d9781ffe083d51e4bf branch.
> There are lots of spurious changes, such as timestamps and CSS styles in tables, so a
generic git diff is not very useful. To see a list of files that have been added, deleted,
renamed, changed type, or are otherwise interesting, use the following command:
>   git diff --name-status --diff-filter=ADCRTXUB origin/asf-site
> To see only files that had 100 or more lines changed:
>   git diff --stat origin/asf-site | grep -E '[1-9][0-9]{2,}'
> When you are satisfied, publish your changes to origin/asf-site using these commands:
>   git commit --allow-empty -m "Empty commit" # to work around a current ASF INFRA bug
>   git push origin asf-site-bdd7782f054a4740bb63f4d9781ffe083d51e4bf:asf-site
>   git checkout asf-site
>   git branch -d asf-site-bdd7782f054a4740bb63f4d9781ffe083d51e4bf
> Changes take a couple of minutes to be propagated. You can verify whether they have been
propagated by looking at the Last Published date at the bottom of http://hbase.apache.org/.
It should match the date in the index.html on the asf-site branch in Git.
> If failed, see https://builds.apache.org/job/hbase_generate_website/297/console


View raw message