[jira] [Commented] (BEAM-4830) Determine why go vet failures invoked by ./gradlew check were not caught be jenkins build build

["Kenneth Knowles (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094642#comment-17094642 ] 

Kenneth Knowles commented on BEAM-4830:
---------------------------------------

Is this now resolved? There is no linked PR. I was passing through the {{build-system}} component and labeling Jenkins and Gradle. This seem old and simple and probably fixed?

> 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: Robert Burke
>            Priority: Major
>              Labels: gradle, jenkins
>
> 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
(v8.3.4#803005)