On Mon, Nov 20, 2017 at 2:36 PM, Daniel Lobato Garcia <elobat...@gmail.com> wrote:
> On 11/20, Ohad Levy wrote: > > On Sun, Nov 19, 2017 at 10:35 PM, Ewoud Kohl van Wijngaarden < > > ew...@kohlvanwijngaarden.nl> wrote: > > > > > On Sun, Nov 19, 2017 at 11:27:57AM +0200, Ohad Levy wrote: > > > > > >> > > >> Can anyone shed some light on ETA for 1.16 GA? > > >> > > >> > > > I should have given an update earlier. > > > > > > So far we've been wanting to include the foreman tasks as a service > from > > > core rather than from foreman-tasks. As always we want that change to > first > > > land in develop but we've been struggling with broken nightlies for > quite > > > some time. It loked like it was fixed since the builds started to pass > > > aagin but we have no validation on the actual UI. Turns out that's > broken > > > and we have no automated testing for this. > > > > > > Would it be an option to ship 1.16 without dynflow service in the core > or > > > would that break things? > > > > > > AFAIU - nothing uses it atm as we were uncertain if it can really be > > used.. there is some code in core regarding that, so I'm not sure if that > > matters... Daniel? > > It definitely can be used as proven by: > Sorry - I didn't mean it like that - my point was that the packaging effort is not resolved, hence we didn't merge or wanted to count on it to block 1.16 (nothing about the technical side of it). > > https://github.com/theforeman/foreman/pull/4240 > https://github.com/Katello/katello/pull/6750 > https://github.com/Katello/katello/pull/6752 > https://github.com/theforeman/foreman/pull/4717 > > Not having a separate service to run Dynflow doesn't have many > implications now > that nothing is using it. > > If foreman-tasks still ships the service to start/stop the dynflow > executor, > we're still fine (same as 1.15). Even without tasks, there's always a > dynflow > executor running with Foreman > (https://github.com/theforeman/foreman/blob/1.16- > stable/config/application.rb#L245) > but this one cannot be stopped or started without restarting Passenger too. > > in other words, it should not block 1.16 at all? > > > > > > > > > > > -- > > > 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. > > > > > > > -- > > 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. > > -- > Daniel Lobato Garcia > > @dLobatog > blog.daniellobato.me > daniellobato.me > > GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30 > Keybase: https://keybase.io/elobato > > -- > 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. > -- 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.
