(Apols for top posting)
That would work - we were going to have to build a CI task to roll the beaker test RPMs
from git so if we can pull them direct that would be much better.
Will investigate when I get home.
Regards,
Nick
--
+44 7736 665171
Sent from mobile device, apologies for brevity.
On 18 Jun 2014, at 14:51, Bill Peck <bpeck(a)redhat.com> wrote:
> On 06/18/2014 03:27 AM, Nicholas Strugnell wrote:
>> On Wed, 2014-06-18 at 17:18 +1000, Nick Coghlan wrote:
>>> On 06/18/2014 01:36 AM, Nicholas Strugnell wrote:
>>> Hi -
>>>
>>> I'm using beaker-import (build 0.17.0-1) pointing at a pulp kickstart
>>> repository (on a satellite 6 beta) and running into some issues:
>>>
>>> [root@beaker ~]# beaker-import
http://foo.com/pulp/repos/ACME_Corporation/Library/content/dist/rhel/serv...
>>> 2014-06-17 16:06:15,113 root CRITICAL No valid importer found for
http://foo.com/pulp/repos/ACME_Corporation/Library/content/dist/rhel/serv...
>> Is that import URL correct? I'm not sure what tree layout changes may
>> happen in the path through Satellite, but the .treeinfo file normally
>> lives under /os/ rather than /kickstart/ (although it doesn't show up in
>> a web browser index listing due to the leading dot).
> Not sure. Satellite provides two repos - one to kickstart from, then one
> to actually register the machine to for updates.
>
> tbh, I don't really want beaker to deploy my test machines, satellite is
> better suited to that as it has all the kickstarts and puppet config for
> each of my different machine profiles already and I don't particularly
> want to have to re-implement them all in beaker - I just want beaker to
> run my test plans on my already-deployed test machines and report.
You might be able to use the stand alone mode of restraint test harness for this.
Look here:
http://restraint.readthedocs.org/en/latest/using.html#running-standalone
That example shows fetching all the tasks from git which I think is easier but you can
also install from rpms like beaker does *if* you make the task repo available to your
machine and export a job xml out of beaker. If you want more details on that let me know,
but I would recommend simply switching to using git uri's for your tasks.
>
> Is there an easy way to do that?
>
> To give some background, we are building a CI environment for builds, so
> satellite, controlled by jenkins, is continuously deploying test
> machines and we want to trigger jenkins to run test plans on these test
> machines and report.
>
> Cheers,
> Nick