You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Alex Amato (JIRA)" <ji...@apache.org> on 2018/07/20 16:15:00 UTC
[jira] [Updated] (BEAM-4830) Determine why go vet failures invoked
by ./gradlew check were not caught be jenkins build build
[ https://issues.apache.org/jira/browse/BEAM-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Amato updated BEAM-4830:
-----------------------------
Summary: Determine why go vet failures invoked by ./gradlew check were not caught be jenkins build build (was: Update Jenkins build to run ./gradlew check instead of just ./gradlew build)
> Determine why go vet failures invoked by ./gradlew check were not caught be jenkins build build
> ------------------------------------------------------------------------------------------------
>
> Key: BEAM-4830
> URL: https://issues.apache.org/jira/browse/BEAM-4830
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Alex Amato
> Assignee: Luke Cwik
> Priority: Major
>
> The purpose of this is to catch errors developers see when they first start contributing to beam. Let's ensure we run the same commands in the [contributing guide|https://beam.apache.org/contribute/].
>
> Note: check runs more than build, so we are not catching these problems in the continuous Jenkins testing.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)