if we can get packit to work then we can start publishing openvox-server-main-nightly where we update the RPM for every commit

yes that would be great, both of it

niiiiice

https://github.com/theforeman/foremanctl/blob/master/.packit.yml is an example of that

we really need 2 steps: add the openvox-server.spec to the repo and implement the create-archive step to build the sources

probably also update our current steps to drop ezbake and rely on openvox-server.spec in our real release workflow

and I'm also tempted to add fmf metadata so we can run tests on them using https://docs.testing-farm.io/ as well

sounds all good to me

so effectively we'll build RPMs for every PR and run tests on those

and then once the PR is merged we'll build a nightly RPM

so this morning I was thinking about writing that up somewhere - would that fit in the planning project?

Josh did some awesome work on the beaker acceptance pipelines to do end to end testing for the rpm/deb packages

yes planning IMO

Yay, after just stopping to care about undocumented settings, gitlab settings provider works! At least I’m able to change signup_enabled to false with it :)

Will fix unit tests and cleanup the PR

The bridge to the puppet-community slack is going down now. You can find us on https://voxpupuli.org/connect/ . See you on the other side o/

set the channel topic: This room isn't synced anymore, please join us on https://voxpupuli.org/connect/

@arjarj has left the channel

@bastelfreak can you please spare some time and release

beaker-hostgenerator

for this PR : https://github.com/voxpupuli/beaker-hostgenerator/pull/415

you need to go to voxpupuli.org/connect. This isn’t monitored any more as per the announcement above on 7/30

@CVQuesty has left the channel

@natemccurdy has left the channel

We use puppet board - just noticed something that I do not think is correct …. Someone updated a module which created a duplicate declaration - on impacted hosts the catalog fails to compile and an err is reported - yet puppet board reports the host as “unchanged” which I suppose you could argue is true, but its because of an error - so I’d argue that it should be reported as failed. I’ve just created an issue for this (430) on the forge - please advise if there is a workaround (or a way to identify hosts in this state) ?

you need to go to voxpupuli.org/connect. This isn’t monitored any more as per the announcement above on 7/30

@Keith Ward has left the channel

@jorhett has left the channel

Anyone using vault with hiera? I was poking at https://github.com/voxpupuli/puppet-hiera_vault and thinking I'm gonna have a problem using it.

you need to go to voxpupuli.org/connect. This channel isn’t monitored any more as per the announcement above on 7/30

Oh. Missed that. Thanks!

@saz has left the channel