Yeah, it's on purpose: we had to disable it back when both the master and branch-2.0 branches had the same versions in their POMs because that was causing the master snapshots to overwrite the 2.0.0-SNAPSHOTS which are generated off of branch-2.0.
I can go ahead and re-enable it later today. On Thu, Jul 21, 2016 at 11:10 AM Andrew Duffy <r...@aduffy.org> wrote: > I’m trying to use a Snapshot build off of master, and after looking > through Jenkins it appears that the last commit where the snapshot was > built is back on 757dc2c09d23400dacac22e51f52062bbe471136, 22 days ago: > https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/job/spark-master-maven-snapshots/ > > > > Looking at the Jenkins page it says that the master-maven build is > disabled, is this purposeful? > > > > -Andrew >