[
https://issues.apache.org/jira/browse/PHOENIX-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177042#comment-17177042
]
Hadoop QA commented on PHOENIX-6056:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/13009764/PHOENIX-6056.master.v2.patch
against master branch at commit 8e34b2bf14e5b6c45c7212104768792390cf0d06.
ATTACHMENT ID: 13009764
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 0 new
or modified tests.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:red}-1 release audit{color}. The applied patch generated 1 release
audit warnings (more than the master's current 0 warnings).
{color:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+ HBASE_VERSION = sh(returnStdout: true, script:
"mvn help:evaluate -Dhbase.profile=${HBASE_PROFILE}
-Dartifact=org.apache.phoenix:phoenix-core -Dexpression=hbase.version -q
-DforceStdout").trim()
+ subject: "Apache-Phoenix | ${BRANCH_NAME} | HBase
${HBASE_PROFILE} | Build ${BUILD_DISPLAY_NAME} ${currentBuild.currentResult}",
+<a href="http://phoenix.apache.org";><img
src='http://phoenix.apache.org/images/phoenix-logo-small.png'/></a>
+<br><b>${BRANCH_NAME}</b> branch <b> HBase ${HBASE_PROFILE} </b> build
${BUILD_DISPLAY_NAME} status <b>${currentBuild.currentResult}</b><hr/>
{color:red}-1 core tests{color}. The patch failed these unit tests:
Test results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4095//testReport/
Code Coverage results:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4095//artifact/phoenix-core/target/site/jacoco/index.html
Release audit warnings:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4095//artifact/patchprocess/patchReleaseAuditWarnings.txt
Console output:
https://builds.apache.org/job/PreCommit-PHOENIX-Build/4095//console
This message is automatically generated.
> Migrate from builds.apache.org by August 15
> -------------------------------------------
>
> Key: PHOENIX-6056
> URL: https://issues.apache.org/jira/browse/PHOENIX-6056
> Project: Phoenix
> Issue Type: Task
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Blocker
> Attachments: PHOENIX-6056.master.v1.patch,
> PHOENIX-6056.master.v2.patch
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {noformat}
> Hi All,
> This NOTICE is for everyone on builds.apache.org. We are migrating to a new
> Cloudbees based Client Master called https://ci-builds.apache.org. The
> migrations of all jobs needs to be done before the switch off date of 15th
> August 2020, so you have a maximum of 4 weeks.
> There is no tool or automated way of migrating your jobs, the
> differences in the platforms, the plugins and the setup makes it impossible
> to do in a safe way. So, you all need to start creating new jobs on
> ci-infra.a.o and then , when you are happy, turn off your old builds on
> builds.a.o.
> There are currently 4 agents over there ready to take jobs, plus a floating
> agent which is shared amongst many masters (more to come). I will migrate
> away 2 more agents from builds.a.o to ci-builds.a.o every few days, and
> will keep an eye of load across both and adjust accordingly.
> If needed, create a ticket on INFRA jira for any issues that crop up, or
> email here on [email protected]. there may be one or two plugins we need to
> install/tweak etc.
> We will be not using 'Views' at the top level, but rather we will take
> advantage of 'Folders Plus' - each project will get its own Folder and have
> authorisation access to create/edit jobs etc within that folder. I will
> create these folders as you ask for them to start with. This setup allows
> for credentials isolation amongst other benefits, including but not limited
> to exclusive agents (Controlled Agents) for your own use , should you have
> any project targeted donations of agents.
> As with other aspects of the ASF, projects can choose to just enable all
> committers access to their folder, just ask.
> We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not
> be setting up any forwarding rules or anything like that.
> So, please, get started *now *on this so you can be sure we are all
> completed before the final cutoff date of 15th August 2020.
> Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA
> tickets.
> Hadoop and related projects have their own migration path to follow, same
> cut off date, Cassandra, Beam, CouchDB have already migrated and are doing
> very well in their new homes.
> Lets get going ...
> --
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
