On Wed, Feb 15, 2017 at 5:55 PM, Adam Williamson wrote:
> On Wed, 2017-02-15 at 12:59 +0100, Josef Skladanka wrote:
> > On Tue, Feb 14, 2017 at 8:51 PM, Adam Williamson <
> adamw...@fedoraproject.org
> > > wrote:
> > > Are you aware of fedmsg-dg-replay? It's a fairly easy way to 'replay'
> > > fe
On Wed, 2017-02-15 at 12:59 +0100, Josef Skladanka wrote:
> On Tue, Feb 14, 2017 at 8:51 PM, Adam Williamson > wrote:
> > Are you aware of fedmsg-dg-replay? It's a fairly easy way to 'replay'
> > fedmsgs for testing. All you need (IIRC) is the fedmsg-relay service
> > running on the same system, a
> So, the repo now has working PoC
> https://pagure.io/taskotron/task-taskotron-ci
> Readme contains example on how to run the task.
> Works on my setup, and I'd be glad if somebody else tried.
I tried, and it didn't eat my laptop. Also it worked. Good job.
/me throws cookies at jskladan
__
On Tue, Feb 14, 2017 at 8:51 PM, Adam Williamson wrote:
> Are you aware of fedmsg-dg-replay? It's a fairly easy way to 'replay'
> fedmsgs for testing. All you need (IIRC) is the fedmsg-relay service
> running on the same system, and you can run
>
I am, but it has this bad quality of changing the
> On Tue, 2017-02-14 at 14:46 -0500, Kamil Paral wrote:
> > > The only problem with this kind of testing is, that we still don't really
> > > have a good way to test trigger, as it is tied to external events. My
> > > idea
> > > here was that I could add something like wiki edit consumer, and trigg
On Tue, 2017-02-14 at 14:46 -0500, Kamil Paral wrote:
> > The only problem with this kind of testing is, that we still don't really
> > have a good way to test trigger, as it is tied to external events. My idea
> > here was that I could add something like wiki edit consumer, and trigger
> > tasks o
> The only problem with this kind of testing is, that we still don't really
> have a good way to test trigger, as it is tied to external events. My idea
> here was that I could add something like wiki edit consumer, and trigger
> tasks off of that, making that one "triggering" edit from inside the
So, the repo now has working PoC
https://pagure.io/taskotron/task-taskotron-ci
Readme contains example on how to run the task.
Works on my setup, and I'd be glad if somebody else tried.
J.
On Fri, Feb 10, 2017 at 7:31 AM, Josef Skladanka
wrote:
>
>
> On Thu, Feb 9, 2017 at 5:58 PM, Matthew Mill
On Thu, Feb 9, 2017 at 5:58 PM, Matthew Miller
wrote:
> On Thu, Feb 09, 2017 at 03:29:13AM +0100, Josef Skladanka wrote:
> > I finally got some work done on the CI task for Taskotron in Taskotron.
> The
> > idea here is that after each commit (of a relevant project - trigger,
> > execdb, resultsd
On Thu, Feb 09, 2017 at 03:29:13AM +0100, Josef Skladanka wrote:
> I finally got some work done on the CI task for Taskotron in Taskotron. The
> idea here is that after each commit (of a relevant project - trigger,
> execdb, resultsdb, libtaskotron) to pagure, we will run the whole stack in
> docke
10 matches
Mail list logo
