[ https://issues.apache.org/jira/browse/SPARK-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14202518#comment-14202518 ]
shane knapp commented on SPARK-4216: ------------------------------------ yep, not running ghprb for spark is a totally legit option as well (which i'd forgotten about -- this was something we'd spoken about josh). just be aware that you're adding a new layer of tooling, which is fine, but it will need to be documented, reviewed and support. i can help support amplab-based stuff (ie: things on our end), but once we're adding in things like remote triggers from appspot, i'll need to draw a support line. :) @nicholas -- those example you showed me are from when the amplab jenkins bot was broken, and not posting. btw, i turned down the number of amplab jenkins bot posts a while back to a minimum, so as not to spam spark builds. so, we: 1) we carry on w/the duplicate postings (annoying, but not dangerous) 2) spark starts using it's own bot/trigger system (needs a lot of work) (1) for now, (2) when you guys can find some time to make it happen? > Eliminate duplicate Jenkins GitHub posts from AMPLab > ---------------------------------------------------- > > Key: SPARK-4216 > URL: https://issues.apache.org/jira/browse/SPARK-4216 > Project: Spark > Issue Type: Bug > Components: Build, Project Infra > Reporter: Nicholas Chammas > Priority: Minor > > * [Real Jenkins | > https://github.com/apache/spark/pull/2988#issuecomment-60873361] > * [Imposter Jenkins | > https://github.com/apache/spark/pull/2988#issuecomment-60873366] -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org