Re: ansible-report git hook design

2019-11-01 Thread Kevin Fenzi
On Wed, Oct 30, 2019 at 12:27:48PM +, T.C. Williams wrote: > On Tue, Oct 29, 2019 at 6:30 AM Clement Verna > wrote: > > > > > > > On Mon, 28 Oct 2019 at 18:42, Kevin Fenzi wrote: > > > >> On Fri, Oct 25, 2019 at 02:33:02PM -0400, Randy Barlow wrote: > >> > On Fri, 2019-10-25 at 19:04 +0200,

Re: ansible-report git hook design

2019-10-30 Thread T.C. Williams
On Tue, Oct 29, 2019 at 6:30 AM Clement Verna wrote: > > > On Mon, 28 Oct 2019 at 18:42, Kevin Fenzi wrote: > >> On Fri, Oct 25, 2019 at 02:33:02PM -0400, Randy Barlow wrote: >> > On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote: >> > > I think the main reason why we don't already have it

Re: ansible-report git hook design

2019-10-29 Thread Clement Verna
On Mon, 28 Oct 2019 at 18:42, Kevin Fenzi wrote: > On Fri, Oct 25, 2019 at 02:33:02PM -0400, Randy Barlow wrote: > > On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote: > > > I think the main reason why we don't already have it on Pagure is > > > that we don't want to be dependent of our own

Re: ansible-report git hook design

2019-10-28 Thread Kevin Fenzi
On Fri, Oct 25, 2019 at 02:33:02PM -0400, Randy Barlow wrote: > On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote: > > I think the main reason why we don't already have it on Pagure is > > that we don't want to be dependent of our own infrastructure to host > > this repo. It currently lives on

Re: ansible-report git hook design

2019-10-25 Thread Randy Barlow
On Fri, 2019-10-25 at 19:04 +0200, Clement Verna wrote: > I think the main reason why we don't already have it on Pagure is > that we don't want to be dependent of our own infrastructure to host > this repo. It currently lives on the batcave01 host which is the box > we use to deploy our infrastruc

Re: ansible-report git hook design

2019-10-25 Thread Clement Verna
On Fri, 25 Oct 2019 at 16:47, Brian (bex) Exelbierd wrote: > > > On Fri, Oct 25, 2019 at 3:28 PM Randy Barlow > wrote: > >> On Fri, 2019-10-25 at 15:03 +0200, Clement Verna wrote: >> > There are basically 2 possibility : >> >> There are other possibilities too, such as putting the repo on >> git

Re: ansible-report git hook design

2019-10-25 Thread Brian (bex) Exelbierd
On Fri, Oct 25, 2019 at 3:28 PM Randy Barlow wrote: > On Fri, 2019-10-25 at 15:03 +0200, Clement Verna wrote: > > There are basically 2 possibility : > > There are other possibilities too, such as putting the repo on > gitlab.com and using their CI on pull requests Can’t we do this on Pagure wi

Re: ansible-report git hook design

2019-10-25 Thread Julen Landa Alustiza
For option 2, it could feasible to cutdown the cloning time from git push . the process will continue to slowdown the push, but not so much. It's just theory, but it might work: 1. We keep an updated master working copy somewhere else: ci working copy 2. On pre-receive hook, we create a branch o

Re: ansible-report git hook design

2019-10-25 Thread Randy Barlow
On Fri, 2019-10-25 at 15:03 +0200, Clement Verna wrote: > There are basically 2 possibility : There are other possibilities too, such as putting the repo on gitlab.com and using their CI on pull requests. signature.asc Description: This is a digitally signed message part

ansible-report git hook design

2019-10-25 Thread Clement Verna
Hi all, Today jlanda, austinpowered and mizdebsk discussed about ticket https://pagure.io/fedora-infrastructure/issue/8157 in #fedora-admin and came up with a few questions on how to implement that solution that I think would be nice to share with the wider group. There are basically 2 possibilit