[
https://issues.apache.org/jira/browse/BEAM-11608?focusedWorklogId=592825&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-592825
]
ASF GitHub Bot logged work on BEAM-11608:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 04/May/21 16:18
Start Date: 04/May/21 16:18
Worklog Time Spent: 10m
Work Description: tysonjh commented on pull request #14584:
URL: https://github.com/apache/beam/pull/14584#issuecomment-832068581
> Thank you! Copying my comment from that PR over here:
>
> > Is it possible to de-dupe this with the logic for the development
container defined in start-build-env.sh? I think there could be value in having
both 1) a development docker container, and 2) a script for installing build
requirements locally if using a compatible OS (this) , but we should strive to
define the requirements in one place.
> > For example, could we use this script to install requirements within the
development container?
Yes, this is a good idea. I like the idea of having a single place to define
requirements.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 592825)
Time Spent: 4h 20m (was: 4h 10m)
> Development environment set up automation
> -----------------------------------------
>
> Key: BEAM-11608
> URL: https://issues.apache.org/jira/browse/BEAM-11608
> Project: Beam
> Issue Type: Wish
> Components: build-system, website
> Reporter: Tyson Hamilton
> Assignee: Eduardo Barrera
> Priority: P3
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> The manual steps in the contribution guide should be combined into a single
> command for users. For example, this could be done by putting all manual
> steps into a shell script.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
