[foreman-dev] Further Broadening Dev Tooling

Along with the conversion of katello-deploy to a more Foreman first and friendly repository, we also have: 1) a Katello devel installer scenario 2) puppet-katello_devel for configuration devel environments I think it would be beneficial to give these the same treatment and move them into the

Re: [foreman-dev] Merge foreman-bats into Forklift

- Original Message - > From: "Dominic Cleal" > To: foreman-dev@googlegroups.com > Sent: Thursday, May 26, 2016 5:42:33 AM > Subject: Re: [foreman-dev] Merge foreman-bats into Forklift > > On 25/05/16 17:25, Ewoud Kohl van Wijngaarden wrote: > > On Wed, May 25, 2016

Re: [foreman-dev] Merge foreman-bats into Forklift

On 25/05/16 17:25, Ewoud Kohl van Wijngaarden wrote: > On Wed, May 25, 2016 at 10:38:04AM -0400, Stephen Benjamin wrote: >> I can understand separating it from development tools, so what about moving >> Katello's bats to foreman-bats? > > What would then be the primary way of getting the latest

Re: [foreman-dev] Jenkins Email Notifications

On 25/05/16 16:35, Eric D Helms wrote: > There was a period of time where Jenkins was sending email notifications > when the email notifier was configured for a job. A few of us have > noticed that this seems to have stopped at some point and does not > appear to be being eaten by spam filters. >