Hi Tal,
We actually had an impressive Webinar just now. We are now checking the
possibility of POC.
Best,
Eyal
On Wed, Jun 13, 2018 at 9:26 AM, Tal wrote:
>
> Hello Eyal
>>>
>Did you succeed to progress with that tool?
>I am asking because our organization is inter
Hi
Thanks,
Which Datastage version do you have?
On Wed, Jun 13, 2018 at 12:12 PM, Eyal Goren wrote:
> Hi Tal,
>
> We actually had an impressive Webinar just now. We are now checking the
> possibility of POC.
>
> Best,
> Eyal
>
> On Wed, Jun 13, 2018 at 9:26 AM, Tal wrote:
>
>>
>> Hello Eyal
>>
11.3 , why?
Eyal
On Wed, Jun 13, 2018 at 1:16 PM, Tal Blat wrote:
> Hi
>
> Thanks,
> Which Datastage version do you have?
>
> On Wed, Jun 13, 2018 at 12:12 PM, Eyal Goren wrote:
>
>> Hi Tal,
>>
>> We actually had an impressive Webinar just now. We are now checking the
>> possibility of POC.
>
I just want to check compatibility ?
we have several versions of Datastage 7.5 8.7 11.5.
did you impressed with the tool (MettleCI) ?
do you know about pricing?
Thanks
On Wed, Jun 13, 2018 at 2:28 PM, Eyal Goren wrote:
> 11.3 , why?
>
> Eyal
>
> On Wed, Jun 13, 2018 at 1:16 PM, Tal Blat wrot
Hi Ignacio,
MettleCI is completely compatible with GitHub Enterprise as well as
Bitbucket.
We're also fully compatible with all version of DataStage and Atlassian
tools currently supported by IBM and Atlassian. Let me know if you'd like
a demo.
Regards - John.
On Friday, 9 March 2018 04:18
Hi Tal,
I can't answer the question about how impressed Eyal was with the demo of
MettleCI, but I *can* talk about MettleCI's DataStage compatibility:
At the time of writing we support all versions from DataStage v8.1 onwards,
with some of MettleCI's more advanced features (e.g. fully automated
Hi Juan,
I think it will be option 3
Have a dive into the tcl code (it's not that hard once you realise it's just
code), search for the bit that does the IgnCase and see if you can spot what
should have been done (at least where the issue may be).
The git list will be interested and suppo
The menu is defijned at ~line 2329
The match function check is ~line 4878
https://github.com/git/git/blob/master/gitk-git/gitk#L4878
It looks like it was coded to do as you ask, but that some update to the tcl
itself (maybe i18n, or utf8 capabilities) has caused the `-nocase` check to
fail.
