flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Metzger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1370) Build website automatically
Date Thu, 08 Jan 2015 15:30:34 GMT

    [ https://issues.apache.org/jira/browse/FLINK-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269437#comment-14269437

Robert Metzger commented on FLINK-1370:

I think the bigger question here is not which technology to use but rather which technology
we can use at all within the ASF infra ;)

The cleanest approach would probably be to run the tools we want on apache servers, but I'm
not sure if thats possible.
Running the tools on a server from somebody in the community is probably difficult because
of security issues (we would need to use the account of one committer)

Let us write an email to infra and discuss with them what we can do.

> 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
> 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

View raw message