You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "David Huntsperger (Jira)" <ji...@apache.org> on 2022/03/15 15:31:00 UTC

[jira] [Updated] (BEAM-5459) Publish javadocs/pydocs to an external source, i.e. buildbot

     [ https://issues.apache.org/jira/browse/BEAM-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Huntsperger updated BEAM-5459:
------------------------------------
    Fix Version/s: Not applicable
       Resolution: Not A Problem
           Status: Resolved  (was: Open)

> Publish javadocs/pydocs to an external source, i.e. buildbot
> ------------------------------------------------------------
>
>                 Key: BEAM-5459
>                 URL: https://issues.apache.org/jira/browse/BEAM-5459
>             Project: Beam
>          Issue Type: Sub-task
>          Components: website
>            Reporter: Scott Wegner
>            Priority: P3
>             Fix For: Not applicable
>
>
> 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



--
This message was sent by Atlassian Jira
(v8.20.1#820001)