Issues for this repository are tracked in Red Hat Jira. Please head to https://issues.redhat.com/browse/MAISTRA in order to browse or open an issue.
master
branch of this repository tracks the master branch of Istio. Currently this is unused.
Branches named maistra-X.X.X
track Maistra releases.
A repository for CentOS builds is available at Fedora COPR.
The following instructions apply to all RPMs in this repository.
- Change directory to the directory for the RPM to build.
- Update the metadata for the RPM see Fields to update for more details. These should be updated to match the GitHub commit ID of the commit to use for the RPM. Some repositories have one commit andothers have multiple commits depending on how many GitHub repositories the build references.
- Execute ./update.sh. This will generate a .tar.gz file containing the sources to use for the build as well as update the sources file. These changes and the changes to the .spec file should be submitted in a pull request.
- Generate the source rpm via:
fedpkg --release el8 srpm
The RPM can be compiled locally using the following command: fedpkg --release el8 local
The RPM can be compiled on COPR using the following command: copr build @coprgroup/coprrepo istio-1.0.0-2.el8.src.rpm
- buildVersion
- buildGitRevision
- git_commit -- this should match the GitHub commit ID in the Istio repo to use for this RPM.
- version -- this is the semantic version for the RPM.
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.
- TAG -- this should match the release-build. For the second build of 1.0.0, this would be 1.0.0-2.
- git_commit -- this should match the GitHub commit ID in the IOR repo to use for this RPM.
- version -- this is the semantic version for the RPM.
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.
- git_commit -- this should match the GitHub commit ID in the Istio operator repo to use for this RPM.
- version -- this is the semantic version for the RPM.
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.
- version -- this is the Grafana version for the RPM (downloaded from https://github.com/grafana/grafana).
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.
- version -- this is the Promu version for the RPM (downloaded from https://github.com/prometheus/promu).
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.
- git_commit -- this should match the GitHub commit ID in the Prometheus repo to use for this RPM.
- version -- this is the Promu version for the RPM (downloaded from https://github.com/prometheus/promu).
- release -- this should be incremented on every build, starting at 1 for a new release.
- changelog -- two new lines should be added for every build explaining the changes in the build.