Re: [foreman-dev] [Infra] Reducing Test Matrix

2017-08-30 Thread Marek Hulán
+1 -- Marek On středa 30. srpna 2017 12:36:01 CEST Ivan Necas wrote: > +1 > > -- Ivan > > On Wed, 30 Aug 2017 at 11:18, Lukas Zapletal wrote: > > Can we do similar for test_plugin_matrix? > > > > I'd like to propose additional change for plugins - to only run core > > tests for one Ruby versi

[foreman-dev] What is the process to get new resources added to transifex?

2017-08-30 Thread Bryan Kearney
I would like to see katello and katello-bastion added to transifex. Once that is done, I can ask folks to add string syncing to the build process. I can translate, but I dont have access to add resources. -- bk -- You received this message because you are subscribed to the Google Groups "fore

Re: [foreman-dev] [Infra] Openshift V2 Sunsetting: Redmine and Prprocessor

2017-08-30 Thread Greg Sutcliffe
On 30/08/17 18:45, Bryan Kearney wrote: >> I would expect that to be easy enough, but I have no access to the >> katello openshift namespace. Once we've moved the rest we can sync on >> getting that migrated. >> >> No word yet on the requested extra resources. >> >> Greg >> > You all waiting on me?

Re: [foreman-dev] [Infra] Openshift V2 Sunsetting: Redmine and Prprocessor

2017-08-30 Thread Bryan Kearney
On 08/30/2017 12:25 PM, Greg Sutcliffe wrote: On Wed, 2017-08-30 at 11:22 -0400, Eric D Helms wrote: In addition, we realized today that there is another project we should migrate (and migrate to Foreman proper) the etherpad that is under the Katello namespace: http://pad-katello.rhcloud.com

Re: [foreman-dev] [Infra] Openshift V2 Sunsetting: Redmine and Prprocessor

2017-08-30 Thread Eric D Helms
Yea - I honestly don't think we even need to migrate the etherpad per say. But rather, just spin up a new etherpad that we can make use of and note to users to port any existing "long lived" pads over themselves. Eric On Wed, Aug 30, 2017 at 12:25 PM, Greg Sutcliffe wrote: > On Wed, 2017-08-30

Re: [foreman-dev] [Infra] Openshift V2 Sunsetting: Redmine and Prprocessor

2017-08-30 Thread Greg Sutcliffe
On Wed, 2017-08-30 at 11:22 -0400, Eric D Helms wrote: > In addition, we realized today that there is another project we > should migrate (and migrate to Foreman proper) the etherpad that is > under the Katello namespace: > > http://pad-katello.rhcloud.com I would expect that to be easy enough, b

[foreman-dev] Re: UX proposals, provisioning wizards - and first time contributors :)

2017-08-30 Thread Greg Sutcliffe
Hi all, The UX demo was recorded today - thanks to all who took part! https://www.youtube.com/watch?v=ZvcAbIuwXsQ There was a good amount of discussion, with the general consesnus that using a wizard for provisioning made a lot of sense. We covered some options for how to get started, and also t

Re: [foreman-dev] [Infra] Openshift V2 Sunsetting: Redmine and Prprocessor

2017-08-30 Thread Eric D Helms
In addition, we realized today that there is another project we should migrate (and migrate to Foreman proper) the etherpad that is under the Katello namespace: http://pad-katello.rhcloud.com On Mon, Aug 28, 2017 at 9:34 AM, Greg Sutcliffe wrote: > Update from today's testing... many thanks to

Re: [foreman-dev] [Infra] Reducing Test Matrix

2017-08-30 Thread Ivan Necas
+1 -- Ivan On Wed, 30 Aug 2017 at 11:18, Lukas Zapletal wrote: > Can we do similar for test_plugin_matrix? > > I'd like to propose additional change for plugins - to only run core > tests for one Ruby version/db as well. For all other version/db > combinations we would only run plugin test suit

Re: [foreman-dev] [Infra] Reducing Test Matrix

2017-08-30 Thread Lukas Zapletal
Can we do similar for test_plugin_matrix? I'd like to propose additional change for plugins - to only run core tests for one Ruby version/db as well. For all other version/db combinations we would only run plugin test suite and not core. LZ On Wed, Aug 23, 2017 at 1:44 AM, Eric D Helms wrote: >

[foreman-dev] Re: [POC] Automatic inspection of user-created provisioning templates

2017-08-30 Thread sshtein
After a great talk on community demo , here is a follow up with the points that were raised during the discussion: Use cases: 1. Run all cops as part of community templates CI against the whole repository 2. Run all cops against a single t