On Sat, Aug 26, 2017 at 3:22 AM, Raúl Kripalani
wrote:
> Yeah, I guess that's doable as well and requires less management effort
> than my suggestion. We could use events [1] to store payload data (e.g. IP,
> version, etc.)
Yes, we could use events or some other similar
The idea is great!
Also I would suggest an ability to run new (modified) tests 100 times in
loop on the CI server to make sure that they don't cause no sporadic
failures (we can include that as part of the requirements before review)
On Sat, Aug 26, 2017 at 6:16 PM, Dmitriy Setrakyan
Sure, Dmitriy
Filed the issue [1]
[1] https://issues.apache.org/jira/browse/IGNITE-6191
On Sat, Aug 26, 2017 at 12:35 AM, Dmitriy Setrakyan
wrote:
> Huge +1
>
> We badly need Linux specific installation packages. Sergey, can you file a
> ticket?
>
> D.
>
> On Tue, Aug
Sergey Kozlov created IGNITE-6191:
-
Summary: Integration for Unix sustem
Key: IGNITE-6191
URL: https://issues.apache.org/jira/browse/IGNITE-6191
Project: Ignite
Issue Type: Task
Love the idea. Let's add Testing Ignite Apps page on Readme. Denis, I don't
think we need many snippets, just a few.
As far as Maven archetype, Yakov, is the only purpose of it to load a
project, so users can add tests to it?
D.
On Fri, Aug 25, 2017 at 8:51 AM, Denis Magda
GitHub user ilantukh opened a pull request:
https://github.com/apache/ignite/pull/2522
Fixed update sequence
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.1.4-updateSeq
Alternatively you can
Yeah, I guess that's doable as well and requires less management effort
than my suggestion. We could use events [1] to store payload data (e.g. IP,
version, etc.) What the download page CGI developed in? PHP?
However, I'm not sure whether storing this data in a 3rd party (Google) is
compliant