Use librarian-puppet to build installer RPM
|Assigned To:||Dominic Cleal|
|Target version:||Foreman - Sprint 20|
|Found in release:||Pull request:|
|Velocity based estimate||-|
We should move to use librarian-puppet instead of submodules to build the installer RPM, probably consuming our published modules from Puppet Forge. This will let us pin modules according to semver in stable branches too, making it easier to make bug fix releases.
We also need to make it easy for installer maintainers to release the modules if we're doing this (currently I do it by hand). Probably a short script in the installer repo or in each module to handle the release would work. It could have the maintainer enter a version number, get them to update the changelog, update the Modulefile, rebuild it, commit it and tag the repo, then upload the resulting module.
#1 Updated by Dominic Cleal about 4 years ago
- Status changed from New to Ready For Testing
- Assigned To set to Dominic Cleal
- Target version set to Sprint 19
A new release script was added in https://github.com/theforeman/foreman-installer/pull/93, and all installer modules on the Forge have been updated.