-
Notifications
You must be signed in to change notification settings - Fork 39
WildFly Operator Release Process
The release process of the WildFly Operator requires permission to push tags and commits to the GitHub wildfly/wildlfy-operator repository as well as the quay.io/wildfly/wildfly-operator repository
$ git clone [email protected]:wildfly/wildfly-operator.git
$ cd wildfly-operator
The tag of the release is set with the environment variable RELEASE_NAME
and follows the x.y.z
pattern.
$ make clean release RELEASE_NAME=x.y.z DRY_RUN=false
The script will create a x.y.z
Git tag of the operator and use this tag to build and push a corresponding Docker image to the quay.io/wildfly/wildfly-operator repository.
Once the script is finished, you can manually verified that the release has been properly done:
-
Check that the corresponding Docker image has been pushed to quay.io/wildfly/wildfly-operator
-
The docker tag must be the same than the
RELEASE_NAME
value (x.y.z
).
-
-
Check that the Git tag has been pushed to github.com/wildfly/wildfly-operator/tags
-
The Git tag must be the same than the
RELEASE_NAME
value (x.y.z
).
-
-
Check that the wildly-operator image is back to
latest
in master branch deploy/operator.yaml
-
Close the corresponding milestone in GitHub milestones
-
The closed milestone must be the same than the
RELEASE_NAME
value (x.y.z
).
-
-
If is not already created, create a new milestone in GitHub milestones (e.g.
x.(y+1).z
for a new minor milestone) -
Write the release notes in GitHub releases