For now I have moved those scripts to
https://github.com/chetanmeh/oak-console-scripts. Later we can
possibly move them to Oak repo if there is a wider interest
Chetan Mehrotra
On Wed, Apr 19, 2017 at 7:42 PM, Davide Giannella wrote:
> On 13/04/2017 10:59, Robert Munteanu wrote:
>> One option is
On 13/04/2017 10:59, Robert Munteanu wrote:
> One option is oak-run/contrib/scripts
+1
On 13/04/2017 10:59, Michael Dürig wrote:
> but when putting such scripts close to our source code most people
> would probably expect them to be "fully supported".
So let's put a disclaimer in the form of:
On Thu, Apr 13, 2017 at 3:29 PM, Robert Munteanu wrote:
> Or we can even have a 'contrib'
> area in the top-level oak directory and place the scripts there, i.e.
> /contrib/scripts or /contrib/oak-run-scripts
That looks like a viable option. I can keep them in a module my github
account but then
Hi,
On 13.04.17 11:33, Chetan Mehrotra wrote:
Major benefit of scripts are they are faster to implement and can be
used in older branches without impacting runtime.
I agree on this part. But most of this benefit comes from not providing
the same level of maintenance, testing, compatibility e
On Thu, 2017-04-13 at 15:03 +0530, Chetan Mehrotra wrote:
> On Thu, Apr 13, 2017 at 2:51 PM, Marcel Reutegger > wrote:
> > one concern I have is maintainability. Scripts tend to go out of
> > date and my
> > question would be how we can detect this when it happens.
>
> Yes that would be the case.
On Thu, Apr 13, 2017 at 2:51 PM, Marcel Reutegger wrote:
> one concern I have is maintainability. Scripts tend to go out of date and my
> question would be how we can detect this when it happens.
Yes that would be the case. The scripts come with lesser testing and
can go stale
> I'm wondering wh
Hi,
one concern I have is maintainability. Scripts tend to go out of date
and my question would be how we can detect this when it happens. As for
the example with the index consistency check you mentioned, I'm
wondering why this is implemented as a script instead of plain Java. I'd
say if we
See OAK-6075 for an example for such a script
Chetan Mehrotra
On Thu, Apr 13, 2017 at 10:35 AM, Chetan Mehrotra
wrote:
> Hi Team,
>
> We have few oak-run console groovy scripts used often to
> analyze/troubleshoot customer setups. Currently these are scattered
> across various github gist.
>
> I
Hi Team,
We have few oak-run console groovy scripts used often to
analyze/troubleshoot customer setups. Currently these are scattered
across various github gist.
I propose that we
1. Create a new module oak-run-scripts (or oak-console-scripts) and
host such generic scripts there. 2. This module
