Chart verifier - release creation is automated through a git hub workflow. To create a new release follow these steps:
-
Modify the pkg/chartverifier/version/version_info.json file with information about the new release, for example:
{ "version": "1.2.0", "quay-image": "quay.io/redhat-certification/chart-verifier", "release-info": [ "Additions to report command metadata output: #174", "New report command: #170" ] }
- version : set the new chart-verifer version.
- quay-image : set to the name of the image (only used for testing).
- release-info : list of significant PR's in the release
-
Create a PR which contains only pkg/chartverifier/version/version_info.json
-
The workflow will detect the file is changed and automatically merge the file and create the release if the following conditions are met:
- The version specified is later that the version in the existing file.
- The PR does not contain any other files.
- The submitter has approval authority for the repository.
- All tests pass.
-
After merging the PR and creating the release the workflow continues in an attempt to add the
latest
tag to the new chart verifier image in quay. This may take a while.- When the release is created, quay will detect the release and build a docker image for the release.
- The workflow retries for up to 15 minutes for the docker image to appear in quay so that it can be linked. If this fails it can be done manually:
- Navigate to the chart verifier image tags in quay
- For the new image hit the options icon on the far right
- A drop down list appears, select "add a new tag"
- A dialogue appears, enter the new tag name as "latest"
- Quay detects latest is laready in use, select "Move" so it points to the new release.
- Navigate to the chart verifier image tags in quay
Notes:
- To link the image to the
latest
tag in quay an auth token is required. This must be set as a repository secret "QUAY_AUTH_TOKEN"- For information on creating an auth token see: Red Hat Quay API guide
- The workflow uses the ChartVerfifierReleaser OAuth Applictaion.
- If the application auth token is changed for any reason the repository secret must also be updated.