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 pre
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 pre
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 pre
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 pre
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 pre
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 pre
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 pre
I asked the question because from your original email, it seemed that the
xml files were newly added.
As you just said, this is another issue (than the one you first mentioned).
So I still wonder what regression you discovered.
Cheers
On Sun, Oct 9, 2016 at 9:37 AM, Andrew Purtell wrote:
> Gre
Great, this is another issue. I will file a JIRA for that. Why did you ask
me to find this out when it took you barely a few minutes? That is a
rhetorical question, no need to actually answer.
On Sun, Oct 9, 2016 at 9:27 AM, Ted Yu wrote:
> Under hbase-site, I found two xml files:
>
> ./0.94/hb
Under hbase-site, I found two xml files:
./0.94/hbase-default.xml
./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
For the second one:
git log
./repo/org/apache/maven/skins/maven-fluido-skin/maven-metadata-local.xml
commit 80bb21927918b30e88602571b9ba766edd3484ed
Author:
This is your problem. Take ownership. Fix it or I'll revert it.
> On Oct 9, 2016, at 9:05 AM, Ted Yu wrote:
>
> 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
ASF policy prohibits binaries in official release artifacts.
On Oct 9, 2016 10:43, "Andrew Purtell" 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
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
wrote:
> I tried to copy latest docs from master into the 1.1.7 RC yesterd
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 o
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 e
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 pre
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 pre
Pushed (and fixed!).
-Dima
On Mon, Sep 12, 2016 at 11:22 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
> t
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 pre
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Build status: Fixed
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
Fixed
If successful, the website and docs have been generated. Save the following
link and apply it by using the following commands:
wget -O-
https://builds.apache.org/job/hbase_generate_website/35/artifact/website.patch.zip
| bsdtar xf -
git checkout asf-site; git pull
git am website.patch
gi
28 matches
Mail list logo