Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Timo Goebel
... have you considered using some kind of a CDN for downloads, e.g. cloudflare, if traffic is a concern? Timo > On 27. Sep 2017, at 17:42, Greg Sutcliffe wrote: > >> On Wed, 2017-09-27 at 17:32 +0200, Michael Moll wrote: >> >>> This would be PR-blocking, I assume?

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Greg Sutcliffe
On Wed, 2017-09-27 at 17:32 +0200, Michael Moll wrote: > > > 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

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Michael Moll
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

Re: [foreman-dev] Release process & permissions

2017-09-27 Thread Greg Sutcliffe
On 27. Sep 2017, at 16:46, Daniel Lobato Garcia > > wrote: > > > > 2 is to extend http://ci.theforeman.org/view/Release%20pipeline/ > > and make it a real pipeline from 0 to release completed. At this > > moment, releases that are not the first RC1 are mostly automated by >

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Greg Sutcliffe
On Wed, 2017-09-27 at 13:46 +0200, Ewoud Kohl van Wijngaarden 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? > > +1 This would be PR-blocking, I assume? I'm fine with

Re: [foreman-dev] Release process & permissions

2017-09-27 Thread Timo Goebel
... isn‘t continuous delivery old these days? Why aren‘t we doing it? I vote in favor of automating this. This ensures predictable results and hopefully makes this process easier. To be honest: The current process scares me. Same for plugin releases. They also are way too manual right now. Timo

[foreman-dev] Release process & permissions

2017-09-27 Thread Daniel Lobato Garcia
Hi devs, After a few releases, and now that I'm trying to help someone else to take over in case it's needed, I found a roadblock. Whoever is doing the release, needs to have **many** permissions. Otherwise, it doesn't make much sense for a person to take over release responsibilities. For

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Lukas Zapletal
Assuming that folks are working on CI redesign, can you guys include that on your TODO please? LZ On Wed, Sep 27, 2017 at 1:46 PM, Ewoud Kohl van Wijngaarden wrote: > On Wed, Sep 27, 2017 at 01:34:08PM +0200, Lukas Zapletal wrote: >> >> what you think about adding

Re: [foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Ewoud Kohl van Wijngaarden
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? +1 Recently we had all red situation when we bumped to Rails 5. After Ivan fixed that, we have the same due to fact import

[foreman-dev] Requesting discovery test for core PRs

2017-09-27 Thread Lukas Zapletal
Hello, what you think about adding discovery to core PRs test suite, just one Ruby version on sqlite3? Recently we had all red situation when we bumped to Rails 5. After Ivan fixed that, we have the same due to fact import refactoring. These changes are good, it's just bad timing when we are