You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/01/02 03:36:13 UTC
[jira] [Comment Edited] (SPARK-5053) Test maintenance branches on
Jenkins using SBT
[ https://issues.apache.org/jira/browse/SPARK-5053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262716#comment-14262716 ]
Josh Rosen edited comment on SPARK-5053 at 1/2/15 2:35 AM:
-----------------------------------------------------------
While we're at it, we should probably consolidate the Maven builds so that we don't have separate "with-YARN" and "pre-YARN" builds; the "Spark-Master-SBT" job tests the same four Hadoop versions, but it does it as a single paramerized Jenkins job, not two parameterized jobs.
*Edit*: actually, we need separate jobs for now since the YARN versions require a different Maven flag, whereas the SBT build takes care of this by using a AMPLAB_JENKINS_BUILD_PROFILE environment variable to set the right flags in run-tests-jenkins.
was (Author: joshrosen):
While we're at it, we should probably consolidate the Maven builds so that we don't have separate "with-YARN" and "pre-YARN" builds; the "Spark-Master-SBT" job tests the same four Hadoop versions, but it does it as a single paramerized Jenkins job, not two parameterized jobs.
> Test maintenance branches on Jenkins using SBT
> ----------------------------------------------
>
> Key: SPARK-5053
> URL: https://issues.apache.org/jira/browse/SPARK-5053
> Project: Spark
> Issue Type: New Feature
> Components: Project Infra
> Reporter: Josh Rosen
> Priority: Blocker
>
> We need to create Jenkins jobs to test maintenance branches using SBT. The current Maven jobs for backport branches do not run the same checks that the pull request builder / SBT builds do (e.g. MiMa checks, PySpark, RAT, etc.) which means that cherry-picking backports can silently break things and we'll only discover it once PRs that are explicitly opened against those branches fail tests; this long delay between introducing test failures and detecting them is a huge productivity issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org