Big +1 from me. Thanks Daniel for bringing this up.
-- Ivan
On Thu, Jun 2, 2016 at 4:57 PM, Dominic Cleal wrote:
> On 02/06/16 15:47, Daniel Lobato Garcia wrote:
> > Hi devs,
> >
> > I'd like to nominate Timo Goebel (timogoebel on Github & IRC) for commit
> > access to theforeman/foreman repo.
What about doing a poll for voting for the cops you're suggesting to
disable? I'm afraid
the mail thread is not a suitable format for this kind of questions.
-- Ivan
On Tue, Jun 21, 2016 at 6:03 PM, Stephen Benjamin
wrote:
>
>
> - Original Message -
> > From: "David Davis"
> > To: fore
ps the options would be
>> > something like “disable” or “do nothing”. Would that make sense to people?
>> >
>> >
>> > David
>> >
>> > On Wed, Jun 22, 2016 at 4:50 AM, Ivan Necas wrote:
>> >> What about doing a poll for voting for the cops
Using the REST API to access the data for further processing is the
recomanded option here.
Can the feature you are looking for be related to
http://projects.theforeman.org/issues/11664?
Just to complete the answer, one can get to the outputs of the job
invocation like this
from the console
Yes it is, see
https://theforeman.org/plugins/foreman_remote_execution/0.3/index.html#3.5CLI
for more details
-- Ivan
On Sat, Jul 9, 2016 at 1:54 AM, wrote:
> Thanks all, I will try these. Especially the hammer command might be
> suitable. I also found the data in the SQLite db within the Dun
Hi,
We observed that every time we have a design discussion around
facets and plugin architecture, we end up with pretty interesting
ideas and a knowledge shared between folks. To support this
activity a bit, we're starting a weekly hangouts to talk about
topics related somehow to facets and plugi
On Wed, Jul 27, 2016 at 11:08 AM, Marek Hulán wrote:
> On Wednesday 27 of July 2016 09:09:20 Dominic Cleal wrote:
>> On 27/07/16 08:54, Marek Hulán wrote:
>> > On Monday 25 of July 2016 07:57:35 Dominic Cleal wrote:
>> >> I've deleted the the "Team AL-GTD - 1" version that somebody had added
>> >>
I guess this should be enough to allow us staring using the backlogs
plugin again
https://github.com/theforeman/prprocessor/pull/48
-- Ivan
On Wed, Jul 27, 2016 at 11:17 AM, Ivan Necas wrote:
> On Wed, Jul 27, 2016 at 11:08 AM, Marek Hulán wrote:
>> On Wednesday 27 of July 2016
I think having everything under one tree makes sense. Long-term, the
goal is to turn
Katello to not feel like a separate project, but rather an extension.
+1
Of course I'm not aware of some possible consequences if there are any?
-- Ivan
On Tue, Aug 2, 2016 at 3:56 PM, Tom McKay wrote:
> As we
On Wed, Aug 3, 2016 at 4:26 PM, Lukas Zapletal wrote:
>> Is there a case for keeping katello separate any longer, or can we combine?
>
> Because it's a plugin? And plugins have its own release cadence, own
> planning (Release versions, Target versions) and Categories. I don't see
> enough benefits
I would say: if we want to make large-scale changes that would make
sense, let's move away
from option hashes to keywords. This would justify the large-scale
changes in my eyes,
and the non-hash rocket syntax just falls more naturally in that case.
And Rubocop
can take a rest here.
I share the lza
On Wed, Aug 24, 2016 at 10:49 AM, Marek Hulán wrote:
> Few more comments below
>
>> What do you mean by "Foreman dev"?
>
> You, me, everyone who contributed to Foreman.
>
>> I’ve contributed to both foreman and
>> rubocop several times. Having worked on rubocop with all its cops enabled
>> hasn’t
The only think I can tell so far is that I can't reproduce this
locally and I have no
idea on what might be different from my vs. jenkins environment that causes this
to happen.
-- Ivan
On Mon, Oct 3, 2016 at 10:28 PM, Stephen Benjamin wrote:
> Tasks, salt and a bunch of plugins are failing test
abase=mysql,ruby=2.3,slave=fast/
Perhaps the change is the access permissions test was in lib, and not
it's part of the unit
Still no idea why it happens in jenkins only
-- Ivan
On Mon, Oct 3, 2016 at 10:35 PM, Ivan Necas wrote:
> The only think I can tell so far is that I can
Lindani Phiri writes:
> Thanks Stephen!
> Will check it out.
>
> L.
>
> On Fri, Oct 7, 2016 at 12:49 PM, Stephen Benjamin
> wrote:
>
>>
>>
>> - Original Message -
>> > From: "Lindani Phiri"
>> > To: "foreman-dev"
>> > Sent: Friday, October 7, 2016 12:33:48 PM
>> > Subject: [foreman-dev
Duncan Innes writes:
> I've seen some tickets about
> the --foreman-proxy-plugin-remote-execution-ssh-remote-working-dir
> operative being ignored, but thought that they had been fixed.
>
> I'm running Foreman 1.13 final (through a Katellite 3.2 RC install) from
> the following install command
Tomas Strachota writes:
> On Fri, Nov 25, 2016 at 3:40 PM, Marek Hulán wrote:
>> Hello foreman devs,
>>
>> As I demonstrated on last community demo [1] templates can be now easily
>> exported from Foreman. I also mentioned that I'm working [2] on
>> foreman_templates feature to easily export all
Hello friends,
You've might noticed we started using foreman-tasks inside the
foreman-core since [1] was merged. Unfortunately, we hit issues in the
packaging phase and the proposed workarounds were not accepted ([2]
[3]).
Based on various discussions, as well as on the fact that
foreman-tasks is
Lukas Zapletal writes:
>>
>> I'm not sure I follow what you mean by administrative tasks. Note that
>> reports
>> import and puppet envs import are core actiones that now run as a foreman
>> task
>> (both synchronous and asynchronous variants). By making the UI part
>> optional
>> users would not
9:26 AM, Marek Hulán wrote:
>> On pátek 20. ledna 2017 2:51:06 CET Ewoud Kohl van Wijngaarden wrote:
>>> On Thu, Jan 19, 2017 at 06:04:58PM +0100, Ivan Necas wrote:
>>> > Lukas Zapletal writes:
>>> > >> I'm not sure I follow what you mean by admini
Eric D Helms writes:
> Reviving this thread.
>
> In one weeks time, I'd like to officially move Forklift to the Foreman
> organization. If there are any objections or concerns, speak now or forever
> hold your peace.
+1000 for moving.
-- Ivan
>
> The following developers currently have write a
Lukas Zapletal writes:
>> If you're concerned about the permissions table, this does not help.
>> Permission are created there by plugin. If the permission is removed later,
>> it
>> should be removed from all roles anyway, user could already assign it to both
>> core and plugin role.
>
> Down b
ow orchestration and current host orchestration.
-- Ivan
>
> Ohad
>
>
>> LZ
>>
>> On Fri, Jan 20, 2017 at 9:26 AM, Marek Hulán wrote:
>> > On pátek 20. ledna 2017 2:51:06 CET Ewoud Kohl van Wijngaarden wrote:
>> >> On Thu, Jan 19, 2017 at 06:04
Marek Hulán writes:
> On úterý 24. ledna 2017 0:02:15 CET Ivan Necas wrote:
>> Lukas Zapletal writes:
>> >> If you're concerned about the permissions table, this does not help.
>> >> Permission are created there by plugin. If the permission is removed
>
Ewoud Kohl van Wijngaarden writes:
> On Tue, Jan 24, 2017 at 12:10:34AM +0100, Ivan Necas wrote:
>> Ohad Levy writes:
>>
>> > On Fri, Jan 20, 2017 at 7:14 PM, Lukas Zapletal wrote:
>> >
>> >> Why we haven't considered ActiveJob API in the
ssht...@redhat.com writes:
> As we all know, foreman core uses rubocop for enforcing style rules. Many
> plugins, especially those that are in theforeman organization, use rubocop
> too.
> The problem is, that the rules are not unified between foreman core and
> plugins. In addition to that whe
synchronization with the core once in a
> while.
Not convinced about benefits of additional layer.
-- Ivan
>
> On Tue, Jan 24, 2017 at 12:08 PM, Ivan Necas wrote:
>
>> ssht...@redhat.com writes:
>>
>> > As we all know, foreman core uses rubocop for enforcing styl
Ivan Necas writes:
> Shimon Shtein writes:
>
>>> expecing there will be foreman on `../foreman` and including
>> `../foreman/.rubocop.yml`in the plugin
>> I wanted to avoid hard assumptions about folders layout (since the task
>> simply won't run at all
Ohad Levy writes:
> On Tue, Jan 24, 2017 at 9:51 AM, Ivan Necas wrote:
>
>> Ewoud Kohl van Wijngaarden writes:
>>
>> > On Tue, Jan 24, 2017 at 12:10:34AM +0100, Ivan Necas wrote:
>> >> Ohad Levy writes:
>> >>
>> >&
, there is not much interested in changing
this in the ecosystem itself.
-- Ivan
>
>
>
> On Tue, Jan 24, 2017 at 6:37 PM, Ivan Necas wrote:
>
>> Ivan Necas writes:
>>
>> > Shimon Shtein writes:
>> >
>> >>> expecing there will be forema
(multiple backends involved).
>
> Ivan, what do you think about providing non-foreman task interface via
> ActiveJob API?
That is the plan.
In the mean time, the original changes were removed: the nightlies should
start working again soon
-- Ivan
>
> LZ
>
> On Tue, Jan
Timo Goebel writes:
> +1 to locking. This is the only workflow that makes sense imho.
> Please note, that we need [1] merged first.
+1 - let's set the right expectations
-- Ivan
>
> - Timo
>
> [1] https://github.com/theforeman/foreman/pull/4283
>
> Am Freitag, 17. Februar 2017 15:05:13 UTC+1 s
gerrit.schwerth...@avid.com writes:
> Hi,
>
> I was studying the dynflow documentation, but there are some pieces or
> examples missing in order for me to understand how to do this and I cannot
> find examples in the Katello sources either. Therefore, I would appreciate
> some help.
>
> I have
Ivan Necas writes:
> Walden Raines writes:
>
>> I do it manually although I probably should just write a commit hook to do
>> it.
>>
>> I put it in the message itself because I think it's useful to have there in
>> case anyone is browsing the git log or
Walden Raines writes:
> I do it manually although I probably should just write a commit hook to do
> it.
>
> I put it in the message itself because I think it's useful to have there in
> case anyone is browsing the git log or in case we ever move away from
> github.
Interesting idea. Before it g
Hi,
I've spend very interesting week fighting some intermittent issues on
foreman_remote_execution
CI. I finally tracked it to [1] yesterday and send a patch to
validates_lengths_from_database.
However, glad that I've finally found the cause and the gem tests were
passing, I haven't spend
that muc
d an issue we had in our code
before but were not hitting because of the nature of the original issue:
now we need to fix it on our side.
-- Ivan
>
> On Fri, Apr 28, 2017 at 11:09 AM, Ivan Necas wrote:
>
>> Hi,
>>
>> I've spend very interesting week fighting some int
Ivan Necas writes:
> Tomer Brisker writes:
>
>> Not sure if it's related or not, but seems that develop is still broken on
>> mysql - lots of errors to do with field lengths, so I'm guessing it
>> may be.
>
> I think it's related in a way that the
Ivan Necas writes:
The issues with validates_lengths_from_database should be over now.
If your tests are still failing, it's your problem now :)
-- Ivan
> Ivan Necas writes:
>
>> Tomer Brisker writes:
>>
>>> Not sure if it's related or not, but seems that
Justin Sherrill writes:
> Hi All,
>
> I have just merged https://github.com/Katello/katello/pull/6716 which
> adds some end to end testing for a small set of scenarios (that will
> likely be expanded over time). It also adds annotations to these
> requests and the ability to generated documen
Tomer Brisker writes:
> Hello,
>
> Ruby 2.0 has been EOL'ed over a year ago. More and more of our dependent
> libraries are dropping support for it, which means that we are either stuck
> with older versions or need to fix support in those libraries which may or
> may not be interested in it. Thi
Timo Goebel writes:
>> On 22. May 2017, at 12:27, Ohad Levy wrote:
>>
>> Since we get a lot of lift from fog, especially for popular providers (e.g.
>> ec2) IMHO its not a good idea to remove fog, which means that we balance
>> between community contributions to fog (e.g. stuff we won't "enjo
Marek Hulán writes:
> +1
+1
>
> On pondělí 26. června 2017 7:41:18 CEST Ondrej Prazak wrote:
>> +1 from me
>>
>> On Mon, Jun 26, 2017 at 3:16 AM, Tom McKay wrote:
>> > +1 for @ehelms
>> >
>> > On Fri, Jun 23, 2017 at 9:05 AM, Neil Hanlon wrote:
>> >> +1 from me :)
>> >>
>> >> On Fri, Jun 2
Bryan Kearney writes:
> There seems to be lots of variaance in the names of tasks, with the
> default adding in the parameters of the tasks. What is the preferred
> pattern for modifying the names?
Hi,
Could you be more specific please? Few examples + what you're trying to
accomplish would be
Ewoud Kohl van Wijngaarden writes:
> +1 on infra being unintuitive.
>
> I'd also add that containers might not be obvious. I'd expect at least a
> few because nobody runs just 1 container. Something like [1] or [2] is
> more like what I'd expect, but at least 3 neatly stacked boxes IMHO.
>
> An
On Tue, 15 Aug 2017 at 09:47, Lukas Zapletal wrote:
> Hey,
>
> nice, but content and infrastructure is a bit weird to me. The folded
> paper icon is overused in many software and its meaning is blurry to
> me.
>
> Infrastructure is more like support software/hardware, smaller
> servers, forklift
>
> On Tuesday, August 15, 2017 at 10:05:02 AM UTC-4, Roxanne Hoover wrote:
>>
>> Thanks for all the great feedback. I'm going to pass this on to the
>> visual team and see what they come up with.
>>
>> On Tuesday, August 15, 2017 at 4:20:26 AM UTC-4, Iv
On Wed, 23 Aug 2017 at 01:44, Eric D Helms wrote:
> I am beginning to look at updating some of our test infrastructure by
> re-writing Jenkins jobs into the pipeline plugin [1]. This is a new style,
> with a different way of both writing and thinking about how jobs are
> crafted. I've started thi
On Wed, 23 Aug 2017 at 15:10, Eric D Helms wrote:
> There are a few different points to reply to, hopefully I did not miss
> one. For the base topic, based on feedback and target for post 1.16, I
> think we end up with:
>
> * 2.2 - postgres
> * 2.3 - postgres
> * 2.4 - postgres
> * 2.2 - mysq
Thanks folks for doing this!
-- Ivan
On Fri, 25 Aug 2017 at 16:10, Greg Sutcliffe
wrote:
> On Fri, 2017-08-25 at 09:39 -0400, Eric D Helms wrote:
> > All,
> >
> > I wanted to make everyone aware that its been announced that
> > Openshift V2 will be closing down on September 30th. We currently r
+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
On Tue, Aug 29, 2017 at 11:25 AM, Daniel Lobato Garcia
wrote:
> On 08/28, Marek Hulán wrote:
>> Hello devs,
>>
>> since there was a discussion on foreman-dev IRC channel recently about
>> merging
>> PRs in Foreman core even if there's some build failed, I talked to few people
>> and decided to de
On Fri, Sep 1, 2017 at 8:56 AM, Marek Hulán wrote:
> Thanks Timo for your input. Please see my comment below in the text.
>
> On čtvrtek 31. srpna 2017 23:08:34 CEST Timo Goebel wrote:
>> Am 28.08.17 um 17:12 schrieb Marek Hulán:
>> > 1) codeclimate is red
>> >
>> > This can be ignored, we never a
so 2. 9. 2017 v 1:27 odesílatel Eric D Helms napsal:
> Howdy,
>
> Some quick background, for those that don't know a majority of our Jenkins
> job configuration are stored in git. I find our Jenkins job configuration
> to be important for developers to be able to understand and contribute
> chang
:+1: for #2
-- Ivan
pá 1. 9. 2017 v 15:37 odesílatel Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> napsal:
> Joining in on the party: +1 for #2
>
> On Fri, Sep 01, 2017 at 09:29:17AM -0400, John Mitsch wrote:
> >Another vote for #2 as you can scan quickly and group by project.
> >
>
On Mon, 4 Sep 2017 at 09:41, Lukas Zapletal wrote:
> I was just trying to bring your attention. With amounts of lists I
> read everyday, this helps me (I actually have a filter that will
> colorize the thread for me).
Since we are already off-topic here, +1 on /cc for folks that needs special
a
Hi,
We've pushed new version of foreman-tasks, that included the last
piece of transition of Dynfow into the core. Unfortunately (or rather
fortunately
- better in CI than in production:) the Katello tests discovered one
issue in the
way the transition of the Dynflow initialization was made.
It c
We are back to green again. Keep calm and carry on merging on green tests again
-- Ivan
On Tue, Sep 12, 2017 at 9:45 PM, Ivan Necas wrote:
> Hi,
>
> We've pushed new version of foreman-tasks, that included the last
> piece of transition of Dynfow into the core. Unfortu
One observation: it seems you need to rebase the foreman PRs in order
the change to be effective
in the tests.
-- Ivan
On Wed, Sep 13, 2017 at 3:35 PM, Ivan Necas wrote:
> We are back to green again. Keep calm and carry on merging on green tests
> again
>
> -- Ivan
>
> On Tu
How would be the authentication/authorization work with this approach?
- - Ivan
On Wed, Sep 13, 2017 at 9:05 PM, wrote:
>
> First attempt to create a design. It's an open discussion, everyone who
> wants to chime in, please do.
>
> The engine: will be deployed as a separate gem. My name suggest
ich should be handled even before the Rack stack
> anyway).
>
> On Thu, Sep 14, 2017 at 10:44 AM, Ivan Necas wrote:
>>
>> How would be the authentication/authorization work with this approach?
>>
>> - - Ivan
>>
>> On Wed, Sep 13, 2017 at 9:05 PM, wrote:
&g
What errors are you seeing. I've tried with ruby 2.2.2, and 2.3.1
bundler 1.15.4, everything worked fine.
What gem --version do you have?
Anything in `bundler.d/Gemfile.local.rb` that could be causing this?
-- Ivan
On Thu, Sep 14, 2017 at 3:13 PM, Lukas Zapletal wrote:
> Hey,
>
> when I do fres
The easiest way to get the recent Gemfile.lock is to look at the build
artifacts in jenkins jobs
(also useful when investigating sudden test failures):
http://ci.theforeman.org/job/test_develop/database=postgresql,ruby=2.4,slave=fast/
-- Ivan
On Thu, Sep 14, 2017 at 3:34 PM, Ivan Necas wrote
c bubbles]# ruby --version
> ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-linux]
>
> This is Intel NUC with 8 GB RAM, bundler runs for about a minute
> before it takes whole memory and start swapping. Then I leave it for
> another 5 minutes before bringing it down.
>
>
That was exacly the reason I was sending the pr Marek referenced: will get
to fixing the broken tests later today. Reviews welcome
-- Ivan
On Thu, 21 Sep 2017 at 10:19, Marek Hulán wrote:
> On čtvrtek 21. září 2017 9:46:59 CEST Lukas Zapletal wrote:
> > Hello,
> >
> > we are getting errors in d
The script sounds like a good start. If every rpm in post runs the
script, and the script
would be clever enough to know it it needs to run it twice or was
already run in the transaction.
We would have a win. Also we could have there some check (such as
properly placed file somewhere),
that could i
I'm ok with the vendorizing approach, as long as it makes the release
process more
effective than it is right now.
Could you expand more on how the core dependencies, plugins and
plugin-dependencies work?
Perhaps this is something we could align with the debian packaging as well to
address some of
On Wed, Oct 18, 2017 at 1:46 AM, Eric D Helms wrote:
> Plugins do present the most complicated part of this process given they
> would each potentially be requiring a few independent gems separate from the
> core stack and we would not want bloat. Seems we'd need either:
>
> 1) a single gem stack
Not hard feelings from me to remove turbo-links:)
-- Ivan
On Thu, Oct 19, 2017 at 7:55 PM, Walden Raines wrote:
> I personally would be okay if we removed turbolinks from foreman entirely.
> We want to replace it in the future with a true single page app anyway. But
> if others want to put in t
Hi,
I was hitting this issue recently in the rex plugin, I needed to
change the way the param is whitelisted,
from using an array, to pass it via a block like this:
https://github.com/theforeman/foreman_remote_execution/pull/276
Also, make sure you're testing it with the version of Foreman th
On Tue, Oct 24, 2017 at 3:16 PM, jbm wrote:
> On 24/10/17 13:20, Ivan Necas wrote:
>> Hi,
>>
>> I was hitting this issue recently in the rex plugin, I needed to
>> change the way the param is whitelisted,
>> from using an array, to pass it via a block like
ion to re-use some of
the existing params allowed for
compute attributes on network? See
https://github.com/theforeman/foreman/blob/18780e5cb7f7d0fbcf97b99426217730b1a54635/app/controllers/concerns/foreman/controller/parameters/nic_base.rb#L27
-- Ivan
On Wed, Oct 25, 2017 at 6:06 PM, jbm wrote:
> O
I lean towards the push model here. The main reason is
the simpler way to publish the instrumentation data from whatever
process we want to track. Also, my understanding is, that we don't care
only if the service is up or down (readiness and liveness) but also
about trends during the processing.
E
On Thu, 2 Nov 2017 at 19:35, Lukas Zapletal wrote:
> Tried to reply with just few words and I am getting:
>
> We’re sorry, but your email message to
> [“theforeman.discourse+680bec16c469f36694d1ecef341e8...@gmail.com”]
> (titled Re: [TheForeman] [Testing Area] October newsletter) didn’t
> work.
>
On Tue, Nov 7, 2017 at 9:19 AM, Ohad Levy wrote:
> Hi,
>
> The challenge:
>
> As a developer, I feel under utilized waiting for tests, the current test
> suite for foreman core takes over an hour, multiply it by number of really
> simple code fixes based on comment and it takes up a good chunk of
On Tue, Nov 7, 2017 at 9:29 AM, Lukas Zapletal wrote:
> We should start tracking test breakages in time, if we have a test
> that did not break for a year, lets delete it. As simple as that. It's
> added value is almost zero.
>
> This is not out of my head, I've heard that on a talk somewhere.
> I
On Tue, Nov 7, 2017 at 10:45 AM, wrote:
>
> I want to start a discussion about the future UX of Host creation/edit form
> from facets perspective.
>
> Let's start with a bit more explanation of facets and how I see the future
> of host data model.
> First of all I'll stat with the purpose of face
Not reacting to everything here, but I would like to keep the
discussion focused on facts.
On Tue, Nov 7, 2017 at 5:17 PM, Greg Sutcliffe wrote:
> Thanks for returning to excellent debating form :)
>
> On 07/11/17 08:50, Lukas Zapletal wrote:
>> HyperKitty is not just a nice archive, you can easi
On Tue, 7 Nov 2017 at 14:56, Eric D Helms wrote:
> On Thu, Nov 2, 2017 at 5:05 PM, Ivan Necas wrote:
>
>> I lean towards the push model here. The main reason is
>> the simpler way to publish the instrumentation data from whatever
>> process we want to track. Also, my u
+1 of marking as unmaintained, but keeping around
-- Ivan
On Wed, Nov 8, 2017 at 12:04 PM, Timo Goebel wrote:
> ... i would not remove it from the github org. There are even more abandoned
> plugins there. I would not delete the code, maybe somebody wants to start
> work on them again.
>
> I w
On Wed, Nov 8, 2017 at 2:42 PM, Greg Sutcliffe wrote:
> Apparently my arguments aren't coming out coherently - I think we've
> misunderstood each other on a couple of points...
>
>> I'm afraid the amount of time waiting doesn't have any influence on
>> the feeling if something is big bang or not.
On Thu, 16 Nov 2017 at 12:13, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> +1 the open issues need to be reviewed. I don't know if this is the best
> solution but can't hurt to get more eyes on them.
>
> What I don't see is something to go over old issues that have been
> tri
po 20. 11. 2017 v 13:36 odesílatel Daniel Lobato Garcia
napsal:
> 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 anyo
On Fri, 24 Nov 2017 at 14:12, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
> On Mon, Nov 20, 2017 at 05:36:29PM +0000, Ivan Necas wrote:
> >po 20. 11. 2017 v 13:36 odesílatel Daniel Lobato Garcia <
> elobat...@gmail.com>
> >napsal:
> >
>
Glad to see this moving forward. Few questions:
1. what happened to the PCP approach we talked about in the past?
2. how would you integrate this to sosreport/foreman-debug? I'm thinking of
storing the statsd data locally, collecting them with foreman-debug, and
then, being able to import them l
My uderstanding of kanban is, that moving the cards manually on the signal
board is actually part of the kanban way of doing things. Another thing,
that is integrated part of the kanban process is
WIP limits, that I don't even see on the redmine plugin. Another reason for
actually not using
redmine
the teams and choosing by what works best
for the particular team, than voting and than forcing everyone to use the same.
You can of course decide in your team to do the voting. If this proves to work
well, I'm sure folks will vote by their feet.
-- Ivan
>
> LZ
>
> On Wed, Nov 29, 201
+2
-- Ivan
On Wed, 6 Dec 2017 at 16:51, Lukas Zapletal wrote:
> +1 +1 beer time!
>
> LZ
>
> On Wed, Dec 6, 2017 at 1:40 PM, Tomer Brisker wrote:
> > Hello,
> > As many of you may have noticed, foreman-core open PR count has been in
> the
> > area of 100-110 for most of the last few months. The
The only concern, as the users are used to the auto-refresh, once we turn
that off, they can start thinking the thing got stuck.
-- Ivan
On Wed, 6 Dec 2017 at 17:50, Ohad Levy wrote:
> On Wed, Dec 6, 2017 at 6:48 PM, Andrew Kofink wrote:
>
>> As part of this I would love to see *all* auto relo
Thanks for sharing, looks very useful indeed and didn't know about it
-- Ivan
On Fri, 8 Dec 2017 at 22:00, Tom McKay wrote:
> @daviddavis reminded me of a nice utility I learned about recently: jq[1].
> I use it quite often in scripts involving container images where I need the
> long sha256 to
I would like to bring one issue into attention for 1.17
https://github.com/theforeman/foreman-packaging/pull/1549#issuecomment-350983953
This was one of the mistakes we did in 1.16, where we removed some code
from foreman-tasks that was supposed to be moved to the core, but it
was not resolved du
91 matches
Mail list logo
