You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: BUILDING.md
-29
Original file line number
Diff line number
Diff line change
@@ -47,35 +47,6 @@ The `make all` command can be used to trigger all the tasks above - build the Ja
47
47
The `mvn` command can be customized by setting the `MVN_ARGS` environment variable when launching `make all`.
48
48
For example, `MVN_ARGS=-DskipTests make all` can be used to avoid running the unit tests.
49
49
50
-
## Release
51
-
52
-
The `make release` target can be used to create a release.
53
-
The `RELEASE_VERSION` environment variable (default value `latest`) can be used to define the release version.
54
-
The `release` target will:
55
-
* Update all the tags of Docker images to `RELEASE_VERSION`
56
-
* Update the documentation version to `RELEASE_VERSION`
57
-
* Set the version of the main Maven project to `RELEASE_VERSION`
58
-
* Create ZIP and TAR.GZ archives with the Strimzi Kafka Bridge which can be used outside of Kubernetes / OpenShift
59
-
60
-
The `release` target will not build the Docker images - they should be built and pushed automatically by Travis CI when the release is tagged in the GitHub repository.
61
-
It also doesn't deploy the Java artifacts anywhere.
62
-
63
-
The release process should normally look like this:
64
-
1. Create a release branch
65
-
2. Export the desired version into the environment variable `RELEASE_VERSION`
66
-
3. Run `make release`
67
-
4. Commit the changes to the existing files (do not add the ZIP and TAR.GZ archives into Git)
68
-
5. Push the changes to the release branch on GitHub
69
-
6. Create the tag and push it to GitHub.
70
-
The tag name determines the tag of the resulting Docker images.
71
-
Therefore the git tag name has to be the same as the `RELEASE_VERSION`,
72
-
7. Once the CI build for the tag is finished and the Docker images are pushed to Docker Hub, create a GitHub release based on the tag.
73
-
Attach the ZIP and TAR.GZ archives to the release.
74
-
8. Build the documentation using `make docu_html` and `make docu_htmlnoheader` and add it to the [Strimzi.io](https://strimzi.io) website.
75
-
8. On the `main` git branch:
76
-
* Update the versions to the next SNAPSHOT version using the `next_version``make` target.
77
-
For example to update the next version to `0.6.0-SNAPSHOT` run: `make NEXT_VERSION=0.6.0-SNAPSHOT next_version`.
78
-
79
50
## Building container images for other platforms with Docker `buildx`
80
51
81
52
Docker supports building images for different platforms using the `docker buildx` command. If you want to use it to
0 commit comments