Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This section describes the commands that are used to build, publish, run tests and examples for the images.


Prerequisites

  • docker;

Build

To build an image X docker images run:

  $ ./gradlew :sdks:python:container:py3:docker :sdks:python:container:docker :sdks:java:container:docker :sdks:go:container:docker --info

This produces local images named

     ${USER}-docker-apache.bintray.io/beam/python3
     ${USER}-docker-apache.bintray.io/beam/python
     ${USER}-docker-apache.. ?
bintray.io/beam/java

     ${USER}-docker-apache.bintray.io/beam/go

You can set the repository root and tag when building with -Pdocker-repository-root= and -Pdocker-tag= on the gradle command line.

They This produces a local image named X. It can be examined by running docker commands:

  $ docker image ls
  $ docker run --entrypoint bash -it ${USER}-docker-apache...bintray.io/beam/python3:latest

Run a test against locally built container

Portability tests are executed with command Y:

  $ ./gradlew ... ?

Running dataflow tests with a custom container requires GCR and dataflow permissions in a cloud project and a GCS location. By default these are apache-beam-testing and gs://temp-storage-for-end-to-end-tests but these can be overridden with PROJECT and GCS_LOCATION environment variables.

  $ bash sdks/python/container/run_validatescontainer.sh python2

  $ bash sdks/python/container/run_validatescontainer.sh python2



TODO: how to run against the prebuilt container?They run against container Z. To use the prebuilt container run this command:

  $ ./gradlew ... ?

Publish

...