Hi, On Wed, Sep 27, 2017 at 04:18:16PM +0100, Greg Sutcliffe wrote: > > On Wed, Sep 27, 2017 at 01:34:08PM +0200, Lukas Zapletal wrote: > > > what you think about adding discovery to core PRs test suite, just > > > one Ruby version on sqlite3? > > > > This would be PR-blocking, I assume? I'm fine with that, just checking.
While I'm +1 about this in general, the two specific cases for Discovery the last weeks were Rails 4.2 -> 5.0 and separation of puppet facts from core. I can't see how a merge block on plugin breakages can be mandatory. Of course it's nice to know that a change is breaking plugins, and ideally the core PR author provides PRs to the affected plugins then, but I worry about further reduction of core development/merge speed, which is already not at its best... > > In other discussions other people have suggested that only testing > > with Katello is odd and I agree. Either we test no plugins or a bunch > > of popular ones. Since testing is good, I'd prefer a bunch of popular > > ones. > > Overall, I agree. However ... > > The primary concern I recall there was about load on Jenkins. We > already exceed our free allowance from Rackspace every single month > (although not by much), so more VMs / compute time there will be hard. > > Do we have any suggestions for lowering the *current* usage so that > there is capacity for this? Some thoughts off the top of my head: > > * Bandwidth takes about 1/3rd of our $2k budget - perhaps we can affect > that Can we somehow see which part is taking most? I.e. is it the CI part or rather the website? Regards -- Michael Moll -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
