[
https://issues.apache.org/jira/browse/FLINK-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15754648#comment-15754648
]
ASF GitHub Bot commented on FLINK-5344:
---------------------------------------
Github user alpinegizmo commented on the issue:
https://github.com/apache/flink/pull/3016
I've been using the incremental build option for several weeks, and find it
to be a significant productivity booster. And yes, it requires ruby 2.0 or
higher (which is nearly four years old at this point), while the buildbot is on
some flavor of 1.9 (no longer supported, even for critical security bugs).
I'm planning to continue to invest significant time in improving the docs,
so I'd like to get this in, but you're right, having two build environments is
suboptimal (and actually we already have two, in a way, since the dockerized
build uses ruby 2.0). I'm hoping we can get the buildbot upgraded to something
less ancient and then drop the 1.9-based Gemfile. @mxm has filed a ticket to
that effect; we'll see.
> docs don't build in dockerized jekyll; -p option is broken
> ----------------------------------------------------------
>
> Key: FLINK-5344
> URL: https://issues.apache.org/jira/browse/FLINK-5344
> Project: Flink
> Issue Type: Bug
> Components: Documentation
> Reporter: David Anderson
> Assignee: David Anderson
> Priority: Minor
>
> The recent Gemfile update doesn't work with the ruby in the provided
> dockerized jekyll environment.
> Also the changes to the build_docs script broke the -p option.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
