Uploaded image for project: 'Beam'
  1. Beam
  2. BEAM-5671 Website automation fit-and-finish
  3. BEAM-5459

Publish javadocs/pydocs to an external source, i.e. buildbot

Details

    • Sub-task
    • Status: Resolved
    • P3
    • Resolution: Not A Problem
    • None
    • Not applicable
    • website
    • None

    Description

      Javadocs and Pydocs are generated for the website at every release, and the generated content gets committed to the git repository in order to publish via the githubpubsub publishing mechanism. Keeping all of this generated content in git is cumbersome and seems unnecessary. Alternatives exist, for example the Flink project uses a buildbot job to build and publish their javadocs:

      https://ci.apache.org/projects/flink/flink-docs-release-1.5/

      The buildbot configuration is here (requires committer access):

      https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/flink.conf

      Attachments

        Activity

          People

            Unassigned Unassigned
            swegner Scott Wegner
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: