Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Agones developer guide to point at faster targets #1656

Merged
merged 2 commits into from
Jun 30, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions build/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -152,10 +152,11 @@ If you are not familiar with GOPATHs, you can read [How to Write Go Code](https:

Make sure you are in the `build` directory to start.

First, let's test all the code. To do this, run `make test`, which will execute all the unit tests for the codebase.
First, let's test the Agones system code. To do this, run `make test-go`, which will execute all the unit tests for
the Go codebase (there are other tests, but they can take a long time to run).

If you haven't run any of the `build` make targets before then this will also create the Docker based build image,
and then run the tests.
If you haven't run any of Make targets before then this will also create the Docker based build
image, and then run the tests.

Building the build image may take a few minutes to download all the dependencies, so feel
free to make cup of tea or coffee at this point. ☕️
Expand All @@ -178,6 +179,9 @@ You may note that docker images, and tar archives are tagged with a concatenatio
upcoming release number and short git hash for the current commit. This has also been set in
the code itself, so that it can be seen in via log statements.

If you don't have a long time to kill, you can run `make build-images` to only build the images for running Agones
, which is often all you need for development.

Congratulations! You have now successfully tested and built Agones!

### Running a Test Google Kubernetes Engine Cluster
Expand Down