On Mon, 10 Feb 2014 15:32:35 -0700
Tim Flink wrote:
> I'm going to start some major refactoring of the playbooks this week
> to farther a couple of goals:
>
> 1. Move to a central execution point for the production, staging and
>non-local dev deployments
>
> 2. Migrate to a style more sim
I wrote an example task that works on bodhi updates today. The idea was
to have something simplistic to use for development, figuring out some
of the data issues (TAP and resultsdb reporting, CheckDetail etc.) and
testing while we get the depcheck and upgradepath tasks complete.
The task just read
One of the design goals that I've talked about before is the idea of
using restful json at the interfaces between components of taskotron.
I'd like to simplify this a bit more to say that any interfaces between
components should be a variation on a dictionary.
When I say dictionary, I'm referring
On Tue, 18 Mar 2014 08:44:01 -0600
Kevin Fenzi wrote:
> On Tue, 18 Mar 2014 00:35:20 -0600
> Tim Flink wrote:
>
> > As a heads up, qadevel.cloud.fedoraproject.org (and our phabricator
> > instance, which is hosted on that machine) seems to be down right
> > now.
> >
> > I'm not sure what exact
On Tue, 11 Mar 2014 07:52:06 -0400 (EDT)
Kamil Paral wrote:
> > > Well, are we sure now how exactly the client setup process will be
> > > hooked into taskotron or its underlying tools?
> >
> > I'm not exactly sure how this will work, either. It's going to
> > depend on what we end up using for
