I agree this is a good idea. I remember my first experience with Beam development - I ran through the steps at [1] and had `./gradlew check` fail. I don't think I ever got it working before moving on and just running more specific tasks. It would be great if we had a reliable way for new contributors to establish an environment that can successfully run `./gradlew check`.
Niels Basjes' PR (https://github.com/apache/beam/pull/13308) seems to be close to that, so I think we should focus on getting that working and iterate from there. Omar concurred with that in https://github.com/apache/beam/pull/12837. [1] https://beam.apache.org/contribute/#development-setup On Wed, Nov 25, 2020 at 3:39 PM Ahmet Altay <al...@google.com> wrote: > Thank you for doing this. > > I have seen a few related PRs. Connecting them here in case these efforts > could be combined: > - https://github.com/apache/beam/pull/12837 (/cc +Omar Ismail > <omarism...@google.com> ) > - https://github.com/apache/beam/pull/13308 > > Ahmet > > On Wed, Nov 25, 2020 at 2:53 PM Sam Rohde <sro...@google.com> wrote: > >> Hi All, >> >> I got tired of my local dev environment being ruined by updates so I made >> a container for Apache Beam development work. What this does is create a >> Docker container from the Ubuntu Groovy image and load it up with all the >> necessary libraries/utilities for Apache Beam development. Then I run an >> interactive shell in the Docker container where I do my work. >> >> This is a nice way for new contributors to easily get started. However >> with the container in its current form, I don't know if this will help >> other people because it is tied closely with my workflow (using VIM, >> YouCompleteMe, for Python). But I think it can be a nice starting point for >> improvements. For example: >> >> - Sharing the host display with Docker to start GUI applications >> (like IntelliJ) in the container >> - Adding Golang development support >> >> Here's a draft PR <https://github.com/apache/beam/pull/13430>, let me >> know what you think, how it can be improved, and whether it's a good idea >> for us to have a dev container like this. >> >> Regards, >> Sam >> >>
