The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
add generic support for installing code via packages instead of from source
|Assignee:||Branan Purvine-Riley||% Done:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This issue is currently not available for export. If you are experiencing the issue described below, please file a new ticket in JIRA. Once a new ticket has been created, please add a link to it that points back to this Redmine ticket.
We recently added the “—yagr” option to allow general specification of git repos to clone for testing. The current implementation simply attempts to run “install.rb” in the source directory, if it exists.
It would be awesome if you could change “—type” from “git” to “git-packages” or something, and if a user specified that, then rather than running “install.rb” it could run “package.rb” or “rake package” to build some system packages… and then it could install them via rpm or deb.
#2 Updated by Justin Stoller over 1 year ago
- Status changed from Needs Decision to Accepted
I’ve linked this to a more specialized ticket that Chris created around RPMs for PuppetDB, but has a much more thorough discussion.
This is a great idea and we will create generic package installation as we iterate on what the PuppetDB team has started. We’ve discussed maybe doing this around Telly with that team but we don’t have a hard schedule.
#4 Updated by Justin Stoller over 1 year ago
- Status changed from Accepted to Rejected
This has been rejected. I thought it was a nice stepping stone but discussion has led to the idea of setting up a basic repo and having the harness (if that) install from those repos as a first step instead. There were concerns around polluting the SUT with rake/rsync and the fact that having a good VPN connection was too demanding of a requirement for a POC.