7.3.2. Tagging and Releasing Components

Warning

The intent of this section is to list the current state of the SIMP Team’s release processes. Since these processes are constantly being improved and automated, you can expect this section content to evolve as well and may be best served by reading the version from the master branch of the simp-doc repository.

This section describes the release procedures for SIMP. The SIMP Team releases:

• Individual Puppet modules as tar files to PuppetForge

• Individual Puppet modules as signed RPMs to the appropriate path at https://download.simp-project.com/simp/yum/.

• Ruby gems for building and testing to RubyGems.org

• SIMP system dependencies as signed RPMs to the appropriate path at https://download.simp-project.com/simp/yum/.

• SIMP-system ISOs to https://download.simp-project.com/simp/ISO/.

SIMP component releases listed above are based off of an official GitHub release the SIMP Team has made to a corresponding SIMP GitHub project. In the case of a SIMP ISO, the component release tag is for the simp-core project, which compiles existing, released component RPMs and dependencies into an ISO.

Note

The SIMP ISO includes RPMs for Puppet modules that are not maintained by SIMP. When a suitable signed RPM does not already exist for such a module (e.g., kmod Puppet module maintained by camptocamp), SIMP builds a signed RPM for that project, using one of that project’s GitHub release tags.

All modules provided by the SIMP Project, are directly sourced from SIMP-controlled repository forks. We do not pull directly from upstream sources.

• 7.3.2.1. Component Versioning
• 7.3.2.2. SIMP-Owned Puppet Module Tag And Release Procedures
• 7.3.2.3. Other Puppet Module Release Procedures
• 7.3.2.4. Ruby Gem Release Procedures
• 7.3.2.5. Other ISO-Related Project Release Procedures
• 7.3.2.6. ISO Release Procedures