Re: fedora_openqa (scheduler/reporter) and createhdds split from openqa_fedora_tools, moved to Pagure

2017-02-14 Thread Adam Williamson
On Tue, 2017-02-14 at 15:55 -0800, Adam Williamson wrote: > I'm trying to clean up all the appropriate bits in Pagure, READMEs, > wiki, ansible tasks etc. this afternoon. If it doesn't all look to be > in line tomorrow AM, please do let me know (or just go ahead and fix > anything straightforward

fedora_openqa (scheduler/reporter) and createhdds split from openqa_fedora_tools, moved to Pagure

2017-02-14 Thread Adam Williamson
Hi folks! So continuing with the agreed plan (for openQA bits) to move git repos to Pagure and split up openqa_fedora_tools, I've split out and moved the scheduler/reporter library and CLI - now called 'fedora_openqa', since 'fedora_openqa_schedule' was a dumb name for a thing that actually does

Re: Taskotron CI in Taskotron

2017-02-14 Thread Adam Williamson
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

Re: Taskotron CI in Taskotron

2017-02-14 Thread Kamil Paral
> 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

Re: Libtaskotron - allow non-cli data input

2017-02-14 Thread Kamil Paral
> On Wed, Feb 8, 2017 at 2:26 PM, Kamil Paral < kpa...@redhat.com > wrote: > > > This is what I meant - keeping item as is, but being able to pass another > > > structure to the formula, which can then be used from it. I'd still like > > > to > > > keep the item to a single string, so it can be