Dogfooding with Katello-based CI

During the retro today we talked about some of the issues where subtle
changes to the API docs have broken some hammer commands, or slightly
altered the options that they take. These are the few I found only in
the last ~2 months or so working on the BATS tests:

http://projects.theforeman.org/issues/8244
http://projects.theforeman.org/issues/8243
http://projects.theforeman.org/issues/7461

We're very lucky in that Red Hat in EMEA has written some scripts
for Jenkins that touch a large array of hammer commands and we know
should work with the version that shipped with Katello 2.0 with little
to no modification (and will have a number of issues against 2.1):

https://github.com/RedHatEMEA/soe-ci

What I would like to do is bring these into upstream as a katello-ci
project to provide some examples for users who want to use Katello with
Jenkins. We can also either ensure they ideally stay working, or get
the changes they need to work with each new release.

CI + Katello would be extremely valuable to bring to the community,
and the crazier idea: to our own infrastructure. I've heard some talk
before about eating our own dogfood but I'd like to bring up the issue
again to start planning how we might do it.

Currently, we're publishing our repos here:
https://fedorapeople.org/groups/katello/releases/yum/

What does everyone think about using Katello to manage the lifecycle of
Katello instead?

I'm thinking we start out small, with publishing our nightly repos
to a Katello instance, and over time work on making this the way
we distribute our software - perhaps exposing a locked down capsule
serving the repos over HTTP, and even pointing Librarian to
Katello-hosted Puppet repos for building the installer.

I haven't seen the guts of our current CI, so I can't say what would all
be involved, but I'd volunteer to work on this. Do we have resources
to setup a testing jenkins server and a Katello instance to start
trying this out?

Thoughts on this idea?

··· -- Stephen Benjamin

Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters

> During the retro today we talked about some of the issues where subtle
> changes to the API docs have broken some hammer commands, or slightly
> altered the options that they take. These are the few I found only in
> the last ~2 months or so working on the BATS tests:
>
> Bug #8244: hammer host update can't update host environment id - Hammer CLI - Foreman
> Bug #8243: hammer puppet-module list no longer takes an organization option - Katello - Foreman
> Bug #7461: Can't add puppet modules to a content view - Katello - Foreman
>
> We're very lucky in that Red Hat in EMEA has written some scripts
> for Jenkins that touch a large array of hammer commands and we know
> should work with the version that shipped with Katello 2.0 with little
> to no modification (and will have a number of issues against 2.1):
>
> https://github.com/RedHatEMEA/soe-ci
>
> What I would like to do is bring these into upstream as a katello-ci
> project to provide some examples for users who want to use Katello with
> Jenkins. We can also either ensure they ideally stay working, or get
> the changes they need to work with each new release.
>
> CI + Katello would be extremely valuable to bring to the community,
> and the crazier idea: to our own infrastructure. I've heard some talk
> before about eating our own dogfood but I'd like to bring up the issue
> again to start planning how we might do it.
>
> Currently, we're publishing our repos here:
> https://fedorapeople.org/groups/katello/releases/yum/
>
> What does everyone think about using Katello to manage the lifecycle of
> Katello instead?
>
> I'm thinking we start out small, with publishing our nightly repos
> to a Katello instance, and over time work on making this the way
> we distribute our software - perhaps exposing a locked down capsule
> serving the repos over HTTP, and even pointing Librarian to
> Katello-hosted Puppet repos for building the installer.
>
> I haven't seen the guts of our current CI, so I can't say what would all
> be involved, but I'd volunteer to work on this. Do we have resources
> to setup a testing jenkins server and a Katello instance to start
> trying this out?
>
> Thoughts on this idea?

+100 on this. I wanted to get that some time ago, but didn't have enough
time/energy to put it into some working state. The most important thing
for me is having the whole setup of the Katello as a CI automated, including
the seeding with data, repos etc, so that it can be easily deployed/reused
for others.

– Ivan

··· ----- Original Message -----


Stephen Benjamin


Red Hat GmbH | http://de.redhat.com/ | Sitz: Grasbrunn
Handelsregister: Amtsgericht München, HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham,
Michael O’Neill, Charles Peters


You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.