Maxim, thanks a lot for picking up this task! Glad to see you contributing
to the website.
-
Denis
On Tue, Apr 14, 2020 at 3:34 PM Maxim Muzafarov wrote:
> Folks,
>
>
> The Apache Ignite download page has been updated.
> Thanks, everyone for the help.
>
>
Folks,
The Apache Ignite download page has been updated.
Thanks, everyone for the help.
https://ignite.apache.org/download.cgi
On Wed, 15 Apr 2020 at 00:22, Nikolay Izhikov wrote:
>
> I’ve added this files to the ignite svn.
>
> > 14 апр. 2020 г., в 01:57, Maxim Muzafarov написал(а):
> >
> >
I’ve added this files to the ignite svn.
> 14 апр. 2020 г., в 01:57, Maxim Muzafarov написал(а):
>
> Folks,
>
>
> As another suggestion, we can place such files (pgp, sha512) here
> https://downloads.apache.org/ignite/gce/ (`gce` directory must be
> created). I don't have access rights there.
Alexey Kukushkin created IGNITE-12898:
-
Summary: Server node with CacheStore fails to re-join the cluster:
IgniteCheckedException: Cannot enable read-through (loader or store is not
provided) for cache
Key: IGNITE-12898
Petr,
I think it's doable. It has custom `install-jdk` script, so even the
latest JDKs can be used.
[1] https://github.com/sormuras/bach#install-jdksh
On Tue, 14 Apr 2020 at 18:31, Petr Ivanov wrote:
>
> We do not need JDK10 — it is out of support already.
> Instead, how about adding JDK14?
>
We do not need JDK10 — it is out of support already.
Instead, how about adding JDK14?
> On 14 Apr 2020, at 17:30, Maxim Muzafarov wrote:
>
> Folks,
>
> I forgot to mention one more important thing of this tool. We can
> configure build and checks simultaneously for several JDK versions.
>
>
Folks,
I forgot to mention one more important thing of this tool. We can
configure build and checks simultaneously for several JDK versions.
jdk:
- oraclejdk8
- openjdk10
- openjdk11
On Tue, 14 Apr 2020 at 17:17, Maxim Muzafarov wrote:
>
> Folks,
>
> +1 Travis-ci
>
> I see no
Ivan Daschinskiy created IGNITE-12897:
-
Summary: Add .NET api to enabling SQL indexing for existing cache.
Key: IGNITE-12897
URL: https://issues.apache.org/jira/browse/IGNITE-12897
Project: Ignite
Folks,
+1 Travis-ci
I see no disadvantages of having multiple CI tools due to:
- it's free for open-source and can be disabled at any time without
any consequences;
- it will free TeamCity from running builds on each PR and TC can
focus on tests execution;
- we can perform more sophisticated
Zaar Hai created IGNITE-12896:
-
Summary: excludeNeighbors=true breaks zone-awareness
Key: IGNITE-12896
URL: https://issues.apache.org/jira/browse/IGNITE-12896
Project: Ignite
Issue Type: Bug
André Schäfer created IGNITE-12895:
--
Summary: AlreadyClosedException: this IndexReader is closed in
Cluster Query
Key: IGNITE-12895
URL: https://issues.apache.org/jira/browse/IGNITE-12895
Project:
> On another hand, it seems weird to have both TeamCity and Travis
And don’t forget MTCGA bot!
> 14 апр. 2020 г., в 10:23, Pavel Tupitsyn написал(а):
>
> We should have PR checks for sure.
>
> On one hand, I agree with Denis:
> - Travis is very easy to set up in GitHub
> - Config file
We should have PR checks for sure.
On one hand, I agree with Denis:
- Travis is very easy to set up in GitHub
- Config file (travis.yml) is stored in git, which is great
On another hand, it seems weird to have both TeamCity and Travis.
Thoughts?
On Tue, Apr 14, 2020 at 10:16 AM Denis Garus
Hello!
I have seen projects with Travis-ci they look cool.
I think Travis-ci is a good solution.
вт, 14 апр. 2020 г. в 10:00, Andrey Mashenkov :
> Maxim,
>
> Good idea. I'd add a license check as well.
>
> On Tue, Apr 14, 2020 at 2:14 AM Maxim Muzafarov wrote:
>
> > Igniters,
> >
> > It's
Maxim,
Good idea. I'd add a license check as well.
On Tue, Apr 14, 2020 at 2:14 AM Maxim Muzafarov wrote:
> Igniters,
>
> It's really `must-have` feature for me to enable Apache Ignite
> pull-request status checks on GitHub. Currently we don't have any of
> them. The most obvious check for
15 matches
Mail list logo
