[
https://issues.apache.org/jira/browse/BIGTOP-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190793#comment-14190793
]
jay vyas commented on BIGTOP-1507:
----------------------------------
https://github.com/apache/bigtop/blob/master/bigtop-bigpetstore/arch.dot <--
like that. for all of bigtops infra and testing. thats what im suggesting for
BIGTOP-1507.
For those that dont know graphviz auto generates a graph, but:
- its pure text -
- so we can maintain it inside of bigtop source
- and commiters can update it when they submit patches.
> 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
> Reporter: jay vyas
>
> 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)
