[
https://issues.apache.org/jira/browse/FLINK-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14281854#comment-14281854
]
Robert Metzger commented on FLINK-1370:
---------------------------------------
I talked to infra and it seems to be impossible to build the complete website
using buildbot, because buildbot does not have access to the servers serving
the websites.
However, there is a special directory accessible both from buildbot and the
web. Here is a list of projects which are doing that:
http://ci.apache.org/projects/
I would like to build the javadocs from the buildbot (on each push to our git).
This would remove most of the files from our svn already.
For now, I would like to keep the documentation part of the website a) because
of google analytics and b) because the comments from disqus are associated with
the URLs (so they would go away if we change the url).
I opened the following JIRA for that:
https://issues.apache.org/jira/browse/INFRA-9033
> 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
> 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)
