|
| 1 | +# Using BuildKite |
| 2 | + |
| 3 | +BuildKite simply runs Docker containers. So it is easy to perform the |
| 4 | +same build locally that BuildKite will do. To handle this, there are |
| 5 | +two different docker-compose files: one for BuildKite and one for local. |
| 6 | +The Dockerfile is the same for both. |
| 7 | + |
| 8 | +## Testing the build locally |
| 9 | +To try out the build locally, start from the root folder of this repo |
| 10 | +(temporal-java-client) and run the following commands. |
| 11 | + |
| 12 | +Build the container for |
| 13 | + |
| 14 | +unit tests: |
| 15 | +```bash |
| 16 | +docker-compose -f docker/buildkite/docker-compose-local.yml build unit-test-test-service |
| 17 | +``` |
| 18 | + |
| 19 | +unit tests with docker sticky on: |
| 20 | +```bash |
| 21 | +docker-compose -f docker/buildkite/docker-compose-local.yml build unit-test-docker-sticky-on |
| 22 | +``` |
| 23 | + |
| 24 | +unit tests with docker sticky off: |
| 25 | +```bash |
| 26 | +docker-compose -f docker/buildkite/docker-compose-local.yml build unit-test-docker-sticky-off |
| 27 | +``` |
| 28 | + |
| 29 | +Run the integration tests: |
| 30 | + |
| 31 | +unit tests: |
| 32 | +```bash |
| 33 | +docker-compose -f docker/buildkite/docker-compose-local.yml run unit-test-test-service |
| 34 | +``` |
| 35 | + |
| 36 | +unit tests with docker sticky on: |
| 37 | +```bash |
| 38 | +docker-compose -f docker/buildkite/docker-compose-local.yml run unit-test-docker-sticky-on |
| 39 | +``` |
| 40 | + |
| 41 | +unit tests with docker sticky off: |
| 42 | +```bash |
| 43 | +docker-compose -f docker/buildkite/docker-compose-local.yml run unit-test-docker-sticky-off |
| 44 | +``` |
| 45 | + |
| 46 | +Note that BuildKite will run basically the same commands. |
| 47 | + |
| 48 | +## Testing the build in BuildKite |
| 49 | +Creating a PR against the master branch will trigger the BuildKite |
| 50 | +build. Members of the Temporal team can view the build pipeline here: |
| 51 | +https://buildkite.com/temporal/temporal-java-client |
| 52 | + |
| 53 | +Eventually this pipeline should be made public. It will need to ignore |
| 54 | +third party PRs for safety reasons. |
0 commit comments