forked from knative/client
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Explain how to build new prow-tests images (knative#160)
* Explain how to build new prow-tests images * Explain the base image
- Loading branch information
1 parent
07dfedc
commit 2b19286
Showing
1 changed file
with
10 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,13 @@ | ||
# Prow Test Job Image | ||
|
||
This directory contains the custom Docker image used by our Prow test jobs. | ||
|
||
## Building and publishing a new image | ||
|
||
To build and push a new image, just run `make push`. | ||
|
||
For testing purposes you can build an image but not push it; to do so, run `make build`. | ||
|
||
Note that you must have proper permission in the `knative-tests` project to push new images to the GCR. | ||
|
||
The `prow-tests` image is pinned on a specific `kubekins` image; update `Dockerfile` if you need to use a newer/different image. This will basically define the versions of `bazel`, `go`, `kubectl` and other build tools. |