You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2021/03/12 17:19:01 UTC
[jira] [Commented] (BEAM-11607) Developer environment CI testing
[ https://issues.apache.org/jira/browse/BEAM-11607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17300454#comment-17300454 ]
Beam JIRA Bot commented on BEAM-11607:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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)