beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-5459) Publish javadocs/pydocs to an external source, i.e. buildbot
Date Fri, 21 Sep 2018 17:33:00 GMT

    [ https://issues.apache.org/jira/browse/BEAM-5459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16623923#comment-16623923
] 

Thomas Weise commented on BEAM-5459:
------------------------------------

[~swegner] these are Python scripts where projects can add their builders to the buildbot
conf that are then triggered either at a scheduled time or when changes occur to the repository
and perform the build steps they wish.

You should be able to access the configuration as a Beam committer (it is shared between all
projects).

If not, let me know and I will send you a copy to look at.

 

 

> 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: Minor
>
> 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
(v7.6.3#76005)

Mime
View raw message