Hello all, I know sometimes I wonder if I need any workarounds to spin up a working katello dev environment. Sometimes we need to use koji repos, installer patches, or have to librarian-puppet install. These workarounds are often discussed on IRC, but its easy to miss these discussions.
I think a central place to keep track of "What do I need to do to spin up a working dev environment?" would be beneficial to all katello devs and help us not waste time trying different configurations. Since I am on bats/pipeline duty these two weeks I started keeping track of this on the bats duty etherpad [1] What I am proposing is whoever is on bats/pipeline duty also keeps track of what is needed to spin up a working centos7 dev environment, tests this regularly, and updates the etherpad. Let me know what you all think of this idea, and if everyone is willing to participate. Feedback welcome. [1] http://pad-katello.rhcloud.com/p/bats-batting-order Thanks, John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
