[
https://issues.apache.org/jira/browse/BEAM-4830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16551007#comment-16551007
]
Luke Cwik commented on BEAM-4830:
---------------------------------
Use the *visteg* plugin to generate a dot graph of the task tree and you can
see whether it appears or not.
It would probably be best to ensure that *vet* is a dependency of *check* and
*check* is a dependency of *build* within go projects.
This will make sure that *build* always assembles all binaries/artifacts and
runs all tests/codestyle/...
> 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)
