[
https://issues.apache.org/jira/browse/BEAM-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312515#comment-17312515
]
Tyson Hamilton commented on BEAM-11607:
---------------------------------------
Regarding using it for Jenkins - I thought this would be a nice idea as well.
TBH I'm not sure of the downsides but the incremental build does sound like it
would be a problem.
Regarding the snippets mechanism, that would be ideal I think. Have a simple
script that does everything with comments in it, show the snippets in page.
For the docker container image, I'm not sure why the shell script
[https://github.com/apache/beam/blob/master/start-build-env.sh] is so
complicated. IMO having a plain old Dockerfile plus some instructions on how to
use it would be better. Maybe [~emilymye] could add some thoughts here.
> Developer environment CI testing
> --------------------------------
>
> Key: BEAM-11607
> URL: https://issues.apache.org/jira/browse/BEAM-11607
> Project: Beam
> Issue Type: Bug
> Components: build-system, testing
> Reporter: Tyson Hamilton
> Priority: P3
>
> The development environment set up instructions described on
> [https://beam.apache.org/contribute/] should have CI testing to verify that
> they're always working. This could be a major obstacle and deterrent for
> users looking to contribute if it doesn't "just work".
>
> CI tests should cover,
> # Containerized development environment
> # Manual (e.g. shell script) set up environment
>
> The CI test should run something hermetic and fast like a :check task on the
> example code of each SDK.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
