[
https://issues.apache.org/jira/browse/BIGTOP-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191163#comment-14191163
]
jay vyas edited comment on BIGTOP-1507 at 10/31/14 1:25 AM:
------------------------------------------------------------
[~rvs] since your architecting the build environment, can you sketch a rough
design of your plan? I can then formalize it into a maintainable diagram w/
other components. A rough paragraph w details or back of the envelope drawing
is good enough probably !
was (Author: jayunit100):
[~rvs] since your architecting the build environment, can you sketch a rough
design of your plan? I can then formalize it into a maintainable diagram w/
other components.
> 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: 0.9.0
>
>
> 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)
