My preference is to use the puppet-community-git_resource module, it
provides an easy way to transition and can be opinionated about the git
functionality we want. I've heard from many people that the module only
supports redhat, which isn't true. But I think we should view that as a
documentation
I hope we can fix that refresh issue within a reasonable timeframe, and
this change won't affect the new releases of production ask.o.o.
M.
On Wed, Sep 23, 2015 at 4:56 PM Jeremy Stanley wrote:
> On 2015-09-23 12:19:22 + (+), Marton Kiss wrote:
> > Yeah, this temporary fix solves the go
On 2015-09-23 12:19:22 + (+), Marton Kiss wrote:
> Yeah, this temporary fix solves the going offline thingy:
> https://review.openstack.org/#/c/222653/
>
> Sitting in the queue for a while, a +2 approval could help to stop refresh
> triggers on ask.o.o
As a very temporary measure I've app
Yeah, this temporary fix solves the going offline thingy:
https://review.openstack.org/#/c/222653/
Sitting in the queue for a while, a +2 approval could help to stop refresh
triggers on ask.o.o
M.
On Wed, Sep 23, 2015 at 2:12 PM Jeremy Stanley wrote:
> On 2015-09-23 07:40:38 + (+), Mar
On 2015-09-23 07:40:38 + (+), Marton Kiss wrote:
[...]
> So my personal opinion that this workaround not solves our
> original problem of refresh event triggers, basically it is
> working, but totally hiding relevant information, and makes later
> debugging or problem discovery impossible.
I was playing with an alternative workaround, where the askbot exec
resources extended with a conditional check of git HEAD status. I made a
quick poc, you can find it here:
https://github.com/mkissam/puppet-vcsrepo-refresh-poc/blob/master/vcsrepo-refresh-workaround.md
The test results are the fol
