this may push in to early next week... these builds were set up before my time, and i'm currently unraveling how they all work before pushing a commit to fix stuff.
nothing like some code archaeology to make my friday more exciting! :) shane On Fri, Jan 4, 2019 at 11:08 AM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > Thank you, Shane! > > Bests, > Dongjoon. > > On Fri, Jan 4, 2019 at 10:50 AM shane knapp <skn...@berkeley.edu> wrote: > >> yeah, i'll get on that today. thanks for the heads up. >> >> On Fri, Jan 4, 2019 at 10:46 AM Dongjoon Hyun <dongjoon.h...@gmail.com> >> wrote: >> >>> Hi, All >>> >>> As a part of release process, we need to check Packaging/Compile/Test >>> Jenkins status. >>> >>> http://spark.apache.org/release-process.html >>> >>> 1. Spark Packaging: >>> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20Packaging/ >>> 2. Spark QA Compile: >>> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Compile/ >>> 3. Spark QA Test: >>> https://amplab.cs.berkeley.edu/jenkins/view/Spark%20QA%20Test/ >>> >>> Currently, (2) and (3) are working because it uses GitHub ( >>> https://github.com/apache/spark.git). >>> But, (1) seems to be broken because it's looking for old repo( >>> https://git-wip-us.apache.org/repos/asf/spark.git/info/refs) instead of >>> new GitBox. >>> >>> Can we fix this in this week? >>> >>> Bests, >>> Dongjoon. >>> >>> >> >> -- >> Shane Knapp >> UC Berkeley EECS Research / RISELab Staff Technical Lead >> https://rise.cs.berkeley.edu >> > -- Shane Knapp UC Berkeley EECS Research / RISELab Staff Technical Lead https://rise.cs.berkeley.edu
