[
https://issues.apache.org/jira/browse/FLINK-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342191#comment-14342191
]
Max Michels commented on FLINK-1370:
------------------------------------
The docs are now automatically generated for all releases and the latest
master. The automatic generation is triggered on a nightly basis.
The generated docs can be found in the list of published documents:
http://ci.apache.org/projects/
The status of the builds can be found here: http://ci.apache.org/builders/
Our buildbot config resides at:
https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/flink.conf
For the old releases (<=0.6.1), the builds fail because the doc build scripts
are different and there is no standard build procedure. It might be sufficient
to build these old release files once and then remove them from the build
configuration.
> Build website automatically
> ---------------------------
>
> Key: FLINK-1370
> URL: https://issues.apache.org/jira/browse/FLINK-1370
> Project: Flink
> Issue Type: Task
> Components: Project Website
> Reporter: Robert Metzger
> Assignee: Max Michels
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We currently use a super slow SVN repository with 17k files to publish our
> website.
> Almost all files in the repository are generated (javadocs, documentation for
> the different releases).
> It would be nice to use the SVN repository to really only host the markdown
> files and let a script generate the rest.
> To figure this out, we either use something within the ASF infra or come up
> with our own solution.
> Something worth looking into might be this:
> http://www.apache.org/dev/cmsref.html#external-build
> What I would personally prefer would be an automated nightly update of the
> website with the latest SNAPSHOT version for the documentation and javadocs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
