I'm preparing for an automation workshop at DevConf in February
trying to think of good example cases to show off what Taskotron can do.
At the moment, I figure that I'll do at least 1 easy task and 1 not so
easy but not crazy task.
Rpmlint is usually my go-to for a trivial/example task but I was hoping
to use something that's a bit more package specific. The things I've
thought of so far are:
- Put together some package specific stuff for a package that we have
some control over (testcloud, yourls etc.)
- Find some other guinea pig package that just works well for
package-specific tasks since the triggering will be artificial for
Do you have any ideas what those package specific checks could be? Because all I can think
of is running some test suite which can't be used during build time in Koji, but we
have nothing like that in our own packages, we would have to find and use some other
package (and study and write a wrapper for that suite).
- See if there are any existing test cases which would automate easily.
Not sure if you mean release validation test cases, but we can most probably rule them
out, because they all require testing with that specific TC/RC (or an installed system
that matches those package versions), which we can't offer at the moment - not without
nested virt or some heavy modifications in the environment setup process.
So I guess you mean package test cases (everything that starts with "Package
And this is really a great idea. I have went through all of those test cases and the
following seem simple enough and easily automated:
I think that picking one of them could be a nice demonstration of what we are aiming for
with Taskotron. The only downside is that we would be showing them something they still
can't do themselves (since we're not still open to arbitrary third-party task
submissions, nor we support storing tasks in distgit-like system). But as a demonstration
of what is hopefully coming in a reasonably close future, I think this would serve well.