Instead of adding another Jenkins job, adding GitHub Action job will be a better solution because we can share the long-term workload of maintenance.
I'll make a PR for that. Bests, Dongjoon. On Tue, Feb 25, 2020 at 9:10 PM Hyukjin Kwon <gurwls...@gmail.com> wrote: > Hm, we should still run this I believe. PR builders do not run doc build > (more specifically `cd docs && jekyll build`) > > Fortunately, Javadoc, Scaladoc, SparkR documentation and PySpark API > documentation are being tested in PR builder. > However, for MD file itself under `docs` and SQL Built-in > Function documentation ( > https://spark.apache.org/docs/latest/api/sql/index.html) are > not being tested anymore if I am not mistaken. I believe spark-master-docs > <https://amplab.cs.berkeley.edu/jenkins/job/spark-master-docs> was only > the job which tests it. > > Would it be difficult to re-enable? > > 2020년 2월 26일 (수) 오후 12:37, shane knapp ☠ <skn...@berkeley.edu>님이 작성: > >> it's been gone for quite a long time. these docs were being built but >> not published. >> >> relevant discussion: >> >> http://apache-spark-developers-list.1001551.n3.nabble.com/Re-moving-the-spark-jenkins-job-builder-repo-from-dbricks-spark-tp25325p26222.html >> >> shane >> >> On Tue, Feb 25, 2020 at 6:18 PM Hyukjin Kwon <gurwls...@gmail.com> wrote: >> >>> Hi all, >>> >>> I just noticed we apparently don't build the documentation in the >>> Jenkins anymore. >>> I remember we have the job: >>> https://amplab.cs.berkeley.edu/jenkins/job/spark-master-docs >>> Does anybody know what happened to this job? >>> >>> Thanks. >>> >> >> >> -- >> Shane Knapp >> Computer Guy / Voice of Reason >> UC Berkeley EECS Research / RISELab Staff Technical Lead >> https://rise.cs.berkeley.edu >> >
