+1
On Wed, Feb 26, 2020 at 3:14 PM Hyukjin Kwon wrote:
> Sounds good to me!
>
> On Thu, 27 Feb 2020, 02:36 Dongjoon Hyun, wrote:
>
>> 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'
Sounds good to me!
On Thu, 27 Feb 2020, 02:36 Dongjoon Hyun, wrote:
> 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,
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 wrote:
> Hm, we should still run this I believe. PR buil
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
Functi
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 Kw
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.
