You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/03/27 01:38:53 UTC
[jira] [Updated] (BIGTOP-1507) Maintain explicit CI and Bigtop
Architecture info in Bigtop
[ https://issues.apache.org/jira/browse/BIGTOP-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Boudnik updated BIGTOP-1507:
---------------------------------------
Fix Version/s: (was: 1.0.0)
backlog
> Maintain explicit CI and Bigtop Architecture info in Bigtop
> -----------------------------------------------------------
>
> Key: BIGTOP-1507
> URL: https://issues.apache.org/jira/browse/BIGTOP-1507
> Project: Bigtop
> Issue Type: Task
> Components: documentation
> Affects Versions: 0.8.0
> Reporter: jay vyas
> Fix For: backlog
>
> Attachments: bigtop.jpg
>
>
> Since CI Artifacts and Testing are quite sophisticated for bigtop, lets curate as part of the source a graphviz file which diagrams the bigtop architecture and outputs.
> That way - our infra is transparent and we can all pitch in to lend a hand .
> Better yet, maybe we can all play around with different CI's (that is really the value of docker i think - it makes the build server a much less fragile and easily replaced element of the stack).
> And an image is worth 1000 words, so i think rather than another README, a good graphviz file to generate the diagram of CI will be awesome.
> Also, we can in the diagram contain how to use the vagrant docker recipes to test build artifacts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)