Github user pwendell commented on a diff in the pull request:

    https://github.com/apache/spark/pull/5093#discussion_r26996263
  
    --- Diff: dev/tests/pr_new_dependencies.sh ---
    @@ -0,0 +1,85 @@
    +#!/usr/bin/env bash
    +
    +#
    +# Licensed to the Apache Software Foundation (ASF) under one or more
    +# contributor license agreements.  See the NOTICE file distributed with
    +# this work for additional information regarding copyright ownership.
    +# The ASF licenses this file to You under the Apache License, Version 2.0
    +# (the "License"); you may not use this file except in compliance with
    +# the License.  You may obtain a copy of the License at
    +#
    +#    http://www.apache.org/licenses/LICENSE-2.0
    +#
    +# Unless required by applicable law or agreed to in writing, software
    +# distributed under the License is distributed on an "AS IS" BASIS,
    +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    +# See the License for the specific language governing permissions and
    +# limitations under the License.
    +#
    +
    +#
    +# This script follows the base format for testing pull requests against
    +# another branch and returning results to be published. More details can be
    +# found at dev/run-tests-jenkins.
    +#
    +# Arg1: The Github Pull Request Actual Commit
    +#+ known as `ghprbActualCommit` in `run-tests-jenkins`
    +# Arg2: The SHA1 hash
    +#+ known as `sha1` in `run-tests-jenkins`
    +#
    +
    +ghprbActualCommit="$1"
    +sha1="$2"
    +
    +MVN_BIN="`pwd`/build/mvn"
    +CURR_CP_FILE="my-classpath.txt"
    +MASTER_CP_FILE="master-classpath.txt"
    +
    +${MVN_BIN} clean compile dependency:build-classpath 2>/dev/null | \
    --- End diff --
    
    If that's the case, we should probably gate this entire thing in a check as 
to whether any pom.xml files are modified. Then for most builds this will not 
add any time, since most builds do not modify dependencies.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org

Reply via email to