[jira] [Commented] (SPARK-4123) Show dependency changes in pull requests

["Brennon York (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SPARK-4123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14523457#comment-14523457 ] 

Brennon York commented on SPARK-4123:
-------------------------------------

[~pwendell] that was a good decision as much as I'd hoped I'd figure it out. I'd propose a second look at it as part of SPARK-7018 at this rate. Plus, once I can access the Jenkins servers it will give me a much better view into what could be causing the issue. Guys, chime in if that doesn't seem the right way to go.

> Show dependency changes in pull requests
> ----------------------------------------
>
>                 Key: SPARK-4123
>                 URL: https://issues.apache.org/jira/browse/SPARK-4123
>             Project: Spark
>          Issue Type: Improvement
>          Components: Project Infra
>            Reporter: Patrick Wendell
>            Assignee: Brennon York
>            Priority: Critical
>
> We should inspect the classpath of Spark's assembly jar for every pull request. This only takes a few seconds in Maven and it will help weed out dependency changes from the master branch. Ideally we'd post any dependency changes in the pull request message.
> {code}
> $ mvn -Phive -Phadoop-2.4 dependency:build-classpath -pl assembly  | grep -v INFO | tr : "\n" | awk -F/ '{print $NF}' | sort > my-classpath
> $ git checkout apache/master
> $ mvn -Phive -Phadoop-2.4 dependency:build-classpath -pl assembly  | grep -v INFO | tr : "\n" | awk -F/ '{print $NF}' | sort > master-classpath
> $ diff my-classpath master-classpath
> < chill-java-0.3.6.jar
> < chill_2.10-0.3.6.jar
> ---
> > chill-java-0.5.0.jar
> > chill_2.10-0.5.0.jar
> {code}



--
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