[GitHub] [beam] kennknowles opened a new issue, #19053: Determine why go vet failures invoked by ./gradlew check were not caught be jenkins build build

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #19053:
URL: https://github.com/apache/beam/issues/19053

   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.
   
    
   
    
   
   Imported from Jira [BEAM-4830](https://issues.apache.org/jira/browse/BEAM-4830). Original Jira may contain additional context.
   Reported by: ajamato@google.com.


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Determine why go vet failures invoked by ./gradlew check were not caught be jenkins build build [beam]

["Abacn (via GitHub)" <gi...@apache.org>]

Abacn closed issue #19053: Determine why go vet failures invoked by ./gradlew check  were not caught be jenkins build build
URL: https://github.com/apache/beam/issues/19053


-- 
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.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org