ASF GitHub Bot logged work on BEAM-3985:

                Author: ASF GitHub Bot
            Created on: 06/Apr/18 20:28
            Start Date: 06/Apr/18 20:28
    Worklog Time Spent: 10m 
      Work Description: youngoli commented on a change in pull request #412: 
[BEAM-3985] Document Gradle commands for testing and linting.
URL: https://github.com/apache/beam-site/pull/412#discussion_r179867936

 File path: src/contribute/contribution-guide.md
 @@ -244,16 +244,28 @@ All code should have appropriate unit testing coverage. 
New code should have
 new tests in the same contribution. Bug fixes should include a regression test
 to prevent the issue from reoccurring.
-#### Java SDK
+The entire set of unit tests can be run with this command at the root of the
+git repository.
-For contributions to the Java code, run unit tests locally via Maven.
+    $ ./gradlew test
-    $ mvn clean verify
+Run this command to test for lint errors.
+    $ ./gradlew lint
 Review comment:
   I don't think this needs to be mentioned here since the lint task only lints 
the Python code right now.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 88597)
    Time Spent: 1h 20m  (was: 1h 10m)

> Update developer guide to reference new Python linting enviroments
> ------------------------------------------------------------------
>                 Key: BEAM-3985
>                 URL: https://issues.apache.org/jira/browse/BEAM-3985
>             Project: Beam
>          Issue Type: Task
>          Components: sdk-py-core, website
>            Reporter: holdenk
>            Assignee: Udi Meiri
>            Priority: Minor
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
> tox.ini changed, but [https://beam.apache.org/contribute/contribution-guide/] 
> still references the told envs.

This message was sent by Atlassian JIRA

Reply via email to