Isn't the RAT check part of the build which generated the 256K patch ? If not, we should add it.
Which XML file misses the license header ? Is this related to HBASE-16793 ? On Sun, Oct 9, 2016 at 8:43 AM, Andrew Purtell <andrew.purt...@gmail.com> wrote: > I tried to copy latest docs from master into the 1.1.7 RC yesterday but > the result then failed a RAT check on an XML file missing a header and some > jars in src/main/resources . I have not checked today if the situation is > better. Those jars will be binaries appearing in our source tarballs. We ok > with that? > > > On Oct 9, 2016, at 8:14 AM, Ted Yu <yuzhih...@gmail.com> wrote: > > > > I pushed the artifacts. > > > > On Sun, Oct 9, 2016 at 12:56 AM, Apache Jenkins Server < > > jenk...@builds.apache.org> wrote: > > > >> Build status: Fixed > >> > >> If successful, the website and docs have been generated. To update the > >> live site, follow the instructions below. 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/371/ > >> artifact/website.patch.zip | funzip > e06c3676f1273f033e3e185ee9c1ec > >> 52c1c7cb31.patch > >> git fetch > >> git checkout -b asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31 > >> origin/asf-site > >> git am --whitespace=fix e06c3676f1273f033e3e185ee9c1ec52c1c7cb31.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-e06c3676f1273f033e3e1 > 85ee9c1ec52c1c7cb31 > >> 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-e06c3676f1273f033e3e185ee9c1ec > >> 52c1c7cb31:asf-site > >> git checkout asf-site > >> git branch -D asf-site-e06c3676f1273f033e3e185ee9c1ec52c1c7cb31 > >> > >> 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. > >> > >> As a courtesy- reply-all to this email to let other committers know you > >> pushed the site. > >> > >> > >> > >> If failed, see https://builds.apache.org/job/ > hbase_generate_website/371/ > >> console >
