![]() This guarantees that the RPMs generated will be exactly the Once a beta isĬonsidered stable, the release candidate should be built from the tag that was generated during dev branch of a project, those changes are released with the next alpha or beta. When to build from a -dev branch, a tag or hotfix branch ¶Īll alphas and betas are built from the -dev branch of each project. Information about the release configs, and which config to use for building, can be found in the Merged forward using the ‘ours’ strategy. If the version specified in the yaml fileĭoes not match the version in the spec file, the spec file will be updated and the change will be If a release build of that version hadĪlready been built in koji then those RPMs will be used. In the yaml file is the final version that is required. Or what that version should be, the build-infrastructure assumes that whatever version is specified Must indicate the build to use in the version field of the release stream’s definition file,īecause there is no way to automatically determine when a particular component needs to be rebuilt Pulp-2.4-rhel7 tag and you wish to add that exact package in the pulp-2.5-rhel7 tag, you For example, if python-celery-3.1.86_64 is built into the We loosely follow theĪnother thing to know about Koji is that once a particular NEVRA (Name, Epoch, Version, Release,Īrchitecture) is built in Koji, it cannot be built again. For releaseīuilds, use whole numbers for the build number. Is time for the first beta, we would be going from 2.5.0-0.7.alpha to 2.5.0-0.8.beta. For example, if we have built 7 2.5.0 alphas and it Will always be 0.1, and every build thereafter prior to the release will be the last release plusĠ.1, even when switching from alpha to beta. When building a GA version the format isįor pre-release builds, Pulp uses the build number as the release field. When building an alpha, beta, or RC the format is theįollowing: X.Y.Z-0. Version: The version that is being built. Specifies which branch the current branch should be merged into. Parent_branch: This is only used when a project is being built from a hotfix branch. Git_branch: Branch or tag to checkout after cloning the git repository This should be the same as the nameĮxternal_deps: path inside root directory of repository of the json file describing externalĭependencies that need to be included in the RPM repository at the end of build process. Repositories: describes a list of Git repositories to include in the build.Įach repository has the following fields: Rsync-tested-dir: The directory to rsync the RPMs to when the build is complete Rsync-target-dir: The directory to rsync the RPMs to when the build is complete. Koji-target-prefix: This target needs to exist in koji. git git_branch : 2.9 - dev version : 2.9. Koji - target - prefix : pulp - 2.9 rsync - target - dir : 2.9 / dev tsync - tested - dir : 2.9 / stage repositories : - name : pulp external_deps : deps / external_deps. In addition it specifies the directories within The components within thatįile specify the target koji tag as well as the individual git repositories and branches that Of a build that the Pulp build scripts can later assemble. ![]() Pulp_packaging/ci/config/releases/.yaml files. This assembly is accomplished using release definitions specified in the Pulp release and testing builds are collections of components that are versioned independently.įor example, the core Pulp server may be at version 2.6 while pulp_docker may be at version 1.0. You can see the full list of Pulp’s Koji tags Pulp uses one Koji tag per Pulp X.Y release stream, per distribution, per architecture.įor example, the 2.6 releases of pulp will build into the pulp-2.6- tags in koji. A tag is essentially a grouping of package builds. There are some concepts you should internalize before you begin making builds.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |