You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/07/22 18:09:20 UTC

[jira] [Commented] (SPARK-16685) audit release docs are ambiguous

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

Sean Owen commented on SPARK-16685:
-----------------------------------

I'm not actually sure where this is used now. I don't think even people packaging the release need to bother with it. Are you running into a specific problem -- do you need to run this?

Nothing in Spark executes against an external cluster. Transient local ones are set up.
I believe the idea is to have installed whatever artifacts you want to audit locally, then run this, setting the repo location and version appropriately.

> audit release docs are ambiguous
> --------------------------------
>
>                 Key: SPARK-16685
>                 URL: https://issues.apache.org/jira/browse/SPARK-16685
>             Project: Spark
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 1.6.2
>            Reporter: jay vyas
>
> The dev/audit-release tooling is ambiguous.
> - should it run against a real cluster? if so when?
> - what should be in the release repo?  Just jars? tarballs?  ( i assume jars because its a .ivy, but not sure).
> - 
> https://github.com/apache/spark/tree/master/dev/audit-release



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