Implement support for installing staging packages#102
Implement support for installing staging packages#102bastelfreak wants to merge 1 commit intovoxpupuli:masterfrom
Conversation
|
relates to voxpupuli/voxpupuli-acceptance#132 |
| # Build the openvox-agent package filename for a given host and version. | ||
| # | ||
| # The host's +packaging_platform+ attribute must follow the Beaker | ||
| # convention: "<variant>-<release>-<arch>", e.g.: |
There was a problem hiding this comment.
I think those are the values and the logic is working, but I haven't checked the beaker code
| host.install_package(url) | ||
| when 'debian', 'ubuntu' | ||
| # Deb: must be downloaded to a local path first, then installed | ||
| wget_on(host, url) do |filename| |
There was a problem hiding this comment.
If we could just do apt install https://.. :sadface:
|
This was used successfully here: https://github.com/voxpupuli/puppet-example/actions/runs/22258245502/job/64392354430 |
ekohl
left a comment
ekohl
left a comment
There was a problem hiding this comment.
We already have install_puppet_release_repo_on. It used to also support staging and you can find traces of it:
So the idea was that you would include staging to REPOS and somehow a way to select it.
| # @raise [ArgumentError] if the variant is unsupported | ||
| # @api private | ||
| def self.openvox_agent_staging_package_filename(host, version) | ||
| variant, release, arch = host['packaging_platform'].split('-', 3) |
There was a problem hiding this comment.
For my own understanding: I was wondering what kind of instance it is. Sadly https://github.com/voxpupuli/beaker/blob/1dd081b0fa445f6edfbaf82baedb5d695e3f21b0/lib/beaker/host.rb#L71 doesn't guarantee it's a Beaker::Platform so you can't reuse the helpers. That's probably why this whole file duplicates the logic all the time.
|
@ekohl the staging repos from Perforce are different. They were/are actual repositories. In our setup it's just a plain directory with all packages. |
|
Do we have some documentation how the staging repos actually look? What the process is, etc. |
|
you mean the openvox setup? We have a pipeline at https://github.com/OpenVoxProject/openvox/actions/workflows/build.yml and it publishes packages to an S3 bucket. The bucket is synced to https://artifacts.voxpupuli.org/openvox-agent/. I've no insights in the Perforce nightlies. |
3 participants
No description provided.