[
https://issues.apache.org/jira/browse/SPARK-28114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16871944#comment-16871944
]
Dongjoon Hyun commented on SPARK-28114:
---------------------------------------
Thank you so much, [~shaneknapp] and [~srowen].
The new four jobs works as expected.
The job showed `--force` weirdly at that failure like the following, but
`hadoop-1` profile removal seems to make it work back.
-
https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-2.7/6509/console
{code}
+ [[ hadoop-2.7 == hadoop-1 ]]
+ build/mvn --force -DzincPort=3245 -DskipTests -Phadoop-2.7 -Pyarn -Phive
-Phive-thriftserver -Pkinesis-asl -Pmesos clean package
{code}
> Add Jenkins job for `Hadoop-3.2` profile
> ----------------------------------------
>
> Key: SPARK-28114
> URL: https://issues.apache.org/jira/browse/SPARK-28114
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 3.0.0
> Reporter: Dongjoon Hyun
> Assignee: shane knapp
> Priority: Major
>
> Spark 3.0 is a major version change. We want to have the following new Jobs.
> 1. SBT with hadoop-3.2
> 2. Maven with hadoop-3.2 (on JDK8 and JDK11)
> Also, shall we have a limit for the concurrent run for the following existing
> job? Currently, it invokes multiple jobs concurrently. We can save the
> resource by limiting to 1 like the other jobs.
> -
> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test%20(Dashboard)/job/spark-master-test-maven-hadoop-2.7-jdk-11-ubuntu-testing
> We will drop four `branch-2.3` jobs at the end of August, 2019.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
