Congratulations, Kirill!
> On 10 Oct 2022, at 17:15, Pavel Tupitsyn wrote:
>
> The Project Management Committee (PMC) for Apache Ignite
> has invited Kirill Tkalenko to become a committer and we are pleased
> to announce that they have accepted.
>
> Kirill is an active contributor and
Congratulations!
> On 17 Sep 2022, at 16:33, Dmitriy Pavlov wrote:
>
> Hi Igniters!
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Ivan Daschinsky to become a member of the PMC and we are pleased to
> announce that he has accepted.
>
> Ivan contributed the Ignite
216.218.135.140 ci.ignite.apache.org in you /etc/hosts file.
Thank you!
[1] https://issues.apache.org/jira/browse/INFRA-23693
> On 14 Sep 2022, at 16:14, Petr Ivanov wrote:
>
> Dear community,
>
>
> TeamCity 1 (ci.ignite.apache.org) is moving to the new hardware.
> Effective
Is it possible to share old/new hardware specs, or at least the difference?
> Will it become faster?
>
> On Wed, Sep 14, 2022 at 4:14 PM Petr Ivanov wrote:
>
>> Dear community,
>>
>>
>> TeamCity 1 (ci.ignite.apache.org) is moving to the new hardware
Dear community,
TeamCity 1 (ci.ignite.apache.org) is moving to the new hardware.
Effective immediately the queue will be paused, and after last build is
finished the process will start.
Please expect service downtime until tomorrow 09:00 UTC.
Until then, please use TeamCity 2
Hi, Mikhail!
Did you mean Apache Ignite 3?
I think we should not forget to add 2 or 3 respectively, 'cause these are
different products whatsoever.
Thank you!
> On 29 Aug 2022, at 17:32, Mikhail Pochatkin wrote:
>
> Hello Igniters,
>
> Switching Apache Ignite build system to Gradle and
Hi, Taras.
Granted!
> On 22 Aug 2022, at 15:34, Taras Ledkov wrote:
>
> Hi,
>
> 1. Petr, could you grant me TC permissions to run release builds please?
> 2. Pavel, please cherry pick your patch for IGNITE-17559 [1] to the release
> branch ignite-2.14 [2]. Or we could move the issue to the
Congratulations!
> On 20 Aug 2022, at 00:18, Dmitriy Pavlov wrote:
>
> Hi Igniters!
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Taras Ledkov to become a member of the PMC and we are pleased to
> announce that he has accepted.
>
> Taras is a veteran committer,
Congrats!
Well deserved!
> On 17 Aug 2022, at 17:34, Kseniya Romanova wrote:
>
> Hi Igniters!
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Vyacheslav Koptilin to become a member of the PMC and we are pleased to
> announce that he has accepted.
>
> Vyacheslav is a
Hi, Mikhail!
The IEP looks great and there are a lot of work to be done.
I guess we are waiting now for the initial Gradle build implementation to start
applying changes on TC and further work for packaging?
> On 15 Aug 2022, at 13:43, Mikhail Pochatkin wrote:
>
> Hello, Igniters.
>
> I'd
Hi, Sergey.
What bot?
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911) 945-00-59
> On 3 Aug 2022, at 11:33, Sergey Korotkov wrote:
>
> Hello colleagues,
>
> I have troubles invoking builds and re-runs from the team city bot interfa
Hi, Rameish!
Are there vulnerabilities in Apache Ignite's jars, dependency's jars or
container software?
Also — can you share the way you've run checks, please?
> On 9 Jun 2022, at 08:13, Gadamsetty, Rameish
> wrote:
>
> Hi Team,
>
> All, We ran Twist lock scan on Docker Image Apache
Hi!
+1 for removal.
That module is long time obsolete and prevents project from JDK upgrades at
least.
> On 7 Apr 2022, at 15:15, Ilya Kasnacheev wrote:
>
> Hello!
>
> I think it is a good idea, it takes ages to compile and I assume the Scala
> version we use is really outdated now.
>
>
Someone with not x86-64 architecture should help with creating and testing
images — and they can be included to release cycle.
> On 11 Mar 2022, at 20:22, Jeremy Meyer wrote:
>
> Not an answer to your question, but some thoughts.. I have an apple
> Silicon M1 mac. While creating the
Congratulations!
> On 9 Mar 2022, at 17:46, Kseniya Romanova wrote:
>
> Igniters! The Apache Ignite Project Management Committee (PMC) has invited
> Alexander Lapin to become a new committer and are happy to announce that he
> has
> accepted.
>
> Alexander contributed to the Ignite several
ote:
>
>> will definitely not be moved to JDK more than 8th.
>
> I think is a matter to discuss :)
> Why we should stay on JDK8 forever?
>
>
>> 2 февр. 2022 г., в 15:23, Petr Ivanov написал(а):
>>
>> Hi, Davide!
>>
>>
>> Ignite 3 will support at least 1
Hi, Davide!
Ignite 3 will support at least 11th JDK but that can be changed (for the
better) on initial release.
Ignite 2 is subject to discuss, it currently runs on 11th and there should be a
patch that added JDK 17 runtime support, but codebase (compile) will definitely
not be moved to JDK
> Also, having different roots at different TCs looks like a proper
> configuration.
> For example, TC2 may not contain the Ignite-3 project.
>
> On Fri, Dec 17, 2021 at 4:13 PM Petr Ivanov wrote:
>
>> Separate JIRA project will ruin the concept of introducing changes for
>
nd so on.
>>
>> Looks like it does not work as I hoped it would.
>> Thanks for your answers.
>>
>> On Fri, Dec 17, 2021 at 2:35 PM Petr Ivanov wrote:
>>
>>> Pavel,
>>>
>>>
>>> If you are referring to this paragraph
>>>
syn
>> wrote:
>>
>>> Petr,
>>>
>>>> why should I edit code in Apache Ignite 2.x repo to introduce new
>> changes
>>> in Apache Ignite 3.x build settings
>>>
>>> I thought we can store 3.x settings in 3.x repo and so on
n store 3.x settings in 3.x repo and so on.
>
> Looks like it does not work as I hoped it would.
> Thanks for your answers.
>
> On Fri, Dec 17, 2021 at 2:35 PM Petr Ivanov wrote:
>
>> Pavel,
>>
>>
>> If you are referring to this paragraph
>&
t-settings-in-version-control.html#Defining+Settings+to+Apply+to+Builds
>
> On Fri, Dec 17, 2021 at 2:19 PM Petr Ivanov wrote:
>
>> TeamCity DSL just does not work as you wish it should.
>>
>>
>> Changes from branches are not visible: you cannot run new
gt; [1]
> https://ci.ignite.apache.org/viewLog.html?buildId=6329858=Releases_ApacheIgniteMain_ReleaseBuild
>
> On Fri, 17 Dec 2021 at 13:20, Petr Ivanov wrote:
>>
>> Concerning Too many requests error, I see the following problem:
>>
>>
>> Your reque
hts are changed on each server by request in Jira.
>>
>> Storing security credentials.
>> All credentials are stored on each server in the file "
>> / config / projects / /pluginData/secure/credentials.json".
>> That is why it is supposed to configure the synchroniz
feel this is in error, please contact the Apache Infrastructure Team at:
us...@infra.apache.org.
Can someone check with them about it, please?
> On 17 Dec 2021, at 13:14, Petr Ivanov wrote:
>
> Permissions updated.
>
>
>> On 17 Dec 2021, at 13:09, Petr Ivanov wrote:
>&g
Permissions updated.
> On 17 Dec 2021, at 13:09, Petr Ivanov wrote:
>
> Could you please add links to builds that are malfunctioning?
> As much as I see here [1] and here [2] — the release build changed to comply
> with 2.12 changes that are not merged to 2.11.1
>
Could you please add links to builds that are malfunctioning?
As much as I see here [1] and here [2] — the release build changed to comply
with 2.12 changes that are not merged to 2.11.1
[1]
https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/6329822
[2]
Congratulations!
> On 1 Dec 2021, at 01:48, Andrey Gura wrote:
>
> Igniters,
>
> The Apache Ignite Project Management Committee (PMC) has invited
> Semyon Danilov to become a new committer and are happy to announce
> that he
> has accepted.
>
> Semyon contributes actively to the project's
Great news! Congratulations, Maksim!
> On 29 Nov 2021, at 19:13, Kseniya Romanova wrote:
>
> Igniters,
>
> The Project Management Committee (PMC) for Apache Ignite has invited Maxim
> Timonin to become a committer and we are pleased to announce that he has
> accepted.
>
> Maxim makes
:06, Maxim Muzafarov wrote:
>
> Petr,
>
> For the RunAll - 0.2
> For the RunAll(Nightly) - 1.0 (the 1.0 is better that 0.2 for sure)
>
> On Thu, 25 Nov 2021 at 15:54, Petr Ivanov wrote:
>>
>> 0.2 or 1.0?
>>
>>> On 25 Nov 2021, at 14:34, Maxi
0.2 or 1.0?
> On 25 Nov 2021, at 14:34, Maxim Muzafarov wrote:
>
> Pert,
>
> I think for nightly builds this is the only right option for the
> suites mentioned above.
>
> On Thu, 25 Nov 2021 at 14:33, Petr Ivanov wrote:
>>
>> Hi, Maksim.
>>
>
Hi, Maksim.
Run All (Nightly) build will run suites with test scale factor 1.0 — will it be
a problem?
> On 25 Nov 2021, at 14:22, Maxim Muzafarov wrote:
>
> Folks,
>
> I've merged the PR [1] to the master branch and applied scale factor
> 0.2 to the tests that were moved to dedicated
So, to run on Azure I’d download ignite.zip + azure.zip.
>>>
>>> Extending ignite.sh would also be great, kind of like what’s happening with
>>> Ignite 3 as far as I can tell.
>>>
>>> What I’m advocating is not needing to use Maven just to run Ignite on
>
Hi, Ivan.
Lib has been installed on all agents.
> On 17 Nov 2021, at 18:38, Ivan Daschinsky wrote:
>
> Hi, folks.
>
> Currently, I'm developing custom numa-aware allocator and development is
> almost done. [1]
>
> In order to run and build tests, it is required to install libnuma-dev
Thanks, Sergey.
I've also reconfigured nightly builds for ignite-2.12 branch.
> On 22 Oct 2021, at 17:32, Сергей Утцель wrote:
>
> I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
Hi. Ivan.
Thanks!
I will attend to the issue in nearest time.
> On 22 Oct 2021, at 12:25, Ivan Daschinsky wrote:
>
> Hi folks!
>
> Recently I've discovered that nightly builds are generated with invalid
> version
> Namely 3.0.0.x instead of 2.12.0.x.
> The main reason -- recent
s their part of
>> opensource sponsoring program.
>>
>> Most likely, we'll setup some domain name as tc.i.a.o or ci2.i.a.o. Please
>> share your vision what would be most obvious.
>>
>> After a private discussions with Vitaliy Osipov and Petr Ivanov, I do
>>
Try now, please.
> On 21 Oct 2021, at 17:47, Nikita Amelchev wrote:
>
> Hi,
>
> Petr, could you grant me TC permissions to run release builds please?
>
> ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn :
>
>>
>> Igniters,
>>
>> I've filed a blocker - release configurations on TeamCity should
gt;>>
>>>>> Let's discuss this until the end of the week. If there is no clear
>>>> picture on option #2 by then, I suggest we go with #1.
>>>>
>>>> For a moment I felt that the proposal is pushed. Let's not do so. The
>>>> subject
Our self-contained zip file currently is over 400Mb and continues to grow.
Even considering that internet speeds has grown too, it is nonsense to force
user to download such an archive where 90% are useless for most cases.
Also we can:
— pack all extensions in single binary with latests
+1
Those parts still very optional nowadays.
> On 20 Sep 2021, at 15:29, Maxim Muzafarov wrote:
>
> Folks,
>
>
> I've created an issue [1] to move all cloud-based IP-finders to the
> ignite-extensions. The motivation is the same as with migration of
> Spring Data integration - to remove
+1
> On 5 Oct 2021, at 02:52, Valentin Kulichenko
> wrote:
>
> Hello Community,
>
> As discussed in [1], I would like to propose the creation of a separate
> Jira project and Confluence space for Ignite 3.
>
> Ignite 2 and Ignite 3 are developed in parallel in separate repos, so we
> need a
lated to run scripts?
>> — issues related to release and delivery processes and scripts?
>
> I’m not aware of those too.
> Can you point to then, please?
>
>> Are they going to be addressed during Apache Ignite evolution too?
>
> Yes, from my point o
erfere the progress.
>
> Respect to the developers who have courage to develop such complex things
> from scratch.
>
>> 29 сент. 2021 г., в 12:55, Petr Ivanov написал(а):
>>
>>
>>> I believe that we should improve Ignite evolutionary and not revolutionary.
>
tion until we cover
>>> these details.
>>>
>>> Let's discuss this until the end of the week. If there is no clear picture
>>> on option #2 by then, I suggest we go with #1.
>>>
>>> -Val
>>>
>>> On Tue, Sep 28, 2021 at
;
> 2021-09-27 14:57 GMT+03:00, Petr Ivanov :
>> How will not they clash if version is based only on date?
>>
>>> On 27 Sep 2021, at 14:33, Ivan Pavlukhin wrote:
>>>
>>> Today it is quite common to use calendar-based versioning scheme, e.g.
&
.cockroachlabs.com/docs/releases/index.html
>
> 2021-09-27 10:49 GMT+03:00, Petr Ivanov :
>> That name will definitely confuse Jira users.
>>
>> Let's stick to basic devision by 2.x and 3.x — it seems most intuitive and
>> has lots of examples inside ASF, look at
gt;>> has no plans to cover the entirety of Ignite's features.
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>> --
>>>>>>>> Ilya Kasnacheev
>>>>>>>>
>>>>>>>>
>>>>>&
+1
Since we've agreed that there are two projects (that are Ignite2 and Ignite3),
separate development environments seem to be logical and natural course of
things.
> On 18 Sep 2021, at 12:42, Alexander Polovtcev wrote:
>
> +1
> This is a welcome proposal, because we already have some
+1
Let's keep the project clean and on the verge of preferable tech stack.
> On 15 Sep 2021, at 12:02, Ivan Pavlukhin wrote:
>
> +1 for removing VS project
>
> 2021-09-15 12:01 GMT+03:00, Nikolay Izhikov :
>> +1
>>
>>> 15 сент. 2021 г., в 11:57, Pavel Tupitsyn
>>> написал(а):
>>>
>>> -1
Hi, Maksim.
File a ticket please and I will see it through.
> On 14 Sep 2021, at 17:24, Maksim Timonin wrote:
>
> Hi, Igniters!
>
> This is a request for a new TC suite. This PR [1] introduces new
> functionality (IndexQuery API). I've prepared a suite [1] with tests
> related to this API.
to add Guava as an explicit dependency in
> order to avoid dependency conflicts and to possibly shade it later. If
> there exists a check that will scan for Guava imports in Ignite code, that
> would probably be nice to have.
>
> On Mon, Sep 13, 2021 at 12:54 PM Petr Ivanov wrote:
>
>&
Should we somehow restrict using this dependency in the project with Maven (or
any other tools)?
> On 13 Sep 2021, at 12:47, Alexander Polovtcev wrote:
>
> The voting has finished and the results are the following:
>
> [+1 Allow]: 1
> [-1 Prohibit]: 5
>
> Therefore it is decided to prohibit
Teamcity will be able to build release — we have caching proxy with Artifactory
which seems has cached that artifact already.
I think I can provide it as a file to republish to mvnrepository, but I have no
such permissions.
Who could help us with uploading it?
> On 27 Aug 2021, at 11:23,
Second IP address is missing from domain record, and first is currently down.
The issue is being resolved by INFRA [1]
[1] https://issues.apache.org/jira/browse/INFRA-22230
> On 20 Aug 2021, at 16:10, Pavel Pereslegin wrote:
>
> Hello, Igniters!
>
> Can someone check why TeamCity
Hi, Igniters.
This is an honour to be among committers of Apache Ignite indeed.
Thanks for your trust, will do my best to meet it.
> On 19 Aug 2021, at 12:58, Dmitry Pavlov wrote:
>
> Hello Ignite community,
>
> The Project Management Committee (PMC) for Apache Ignite
>
After initial setup, there won't be lot's of changes, at least for PRs there
will be single commit with both fix and TC changes.
> On 17 Aug 2021, at 13:05, Anton Vinogradov wrote:
>
> This will kill repo history.
> You'll see dozens of TC config updates vs a single Ignite fix
Unfortunately, it won't work. At least in the nearest future.
Currently, you cannot see project structure on TC in any branch except default
(master/main).
And some things like snapshot dependencies are ONLY taken from default branch.
> On 17 Aug 2021, at 10:25, Pavel Tupitsyn wrote:
>
>
Hi, Dmitry.
I think we should start with adding current projects as-is in form of
autogenerated Kotlin code, but continue to use UI for editing.
Later at some point we should replace autogenerated code with valid one (this
can be done configuration by configuration), that will allow use the
Congratulations, Aleksandr!
> On 11 Aug 2021, at 12:10, Pavel Tupitsyn wrote:
>
> The Project Management Committee (PMC) for Apache Ignite has invited
> Alexander Shapkin to become a committer and we are pleased to announce that
> he has accepted.
>
> Alexander is one of the most active user
are your vision what would be most obvious.
>
> After a private discussions with Vitaliy Osipov and Petr Ivanov, I do believe
> that it would be possible to preserve current registered users. Build
> configurations are to be the same for the secondary instance. Technical
> details on how
I've created issue in INFRA project about this matter [1].
Please, stand by,
[1] https://issues.apache.org/jira/browse/INFRA-22150
> On 28 Jul 2021, at 09:42, Alex Plehanov wrote:
>
> Hello, Igniters!
>
> Looks like the MTCGA site hosted on Apache Ignite domain [1] is currently
> down (at
Hi, Igniters!
While working with Semyon on IGNITE-15182 [1] we've stumbled upon the following
dilemma, that I would like to discuss.
Currently, `mvn compile pmd:check` command (as mentioned in Devnotes) also adds
to check generated sources and fails on them, while mvn install && mvn
rov wrote:
>
> Folks,
>
> Artefacts are available here. Is this what we are looking for?
>
> https://apache.jfrog.io/artifactory/ignite-deb/
> https://apache.jfrog.io/artifactory/ignite-rpm/
>
> On Fri, 23 Jul 2021 at 12:15, Petr Ivanov wrote:
>>
>> No
ackage manually (there is script for that inside).
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911) 945-00-59
> On 23 Jul 2021, at 06:09, Mustafa Sunka wrote:
>
> Is there a mirror available? I have an app I am trying to rebuild and am
> una
Check you permissions now, please.
> On 20 Jul 2021, at 10:24, Alexey Gidaspov wrote:
>
> Petr, my login is agidaspov
>
> On 2021/07/20 07:22:26, Petr Ivanov wrote:
>> Aleksey — what is your login / email in TC?
>>
>>
>>> On 19
Aleksey — what is your login / email in TC?
> On 19 Jul 2021, at 16:10, Alexey Gidaspov wrote:
>
> No, but I'm release manager for 2.11 release and I think I should be able to
> run RC build.
>
> On 2021/07/19 12:47:46, Petr Ivanov wrote:
>> Hi!
>>
&
Nikolay, Dmitriy, Anton — what do you think?
> On 19 Jul 2021, at 16:10, Alexey Gidaspov wrote:
>
> No, but I'm release manager for 2.11 release and I think I should be able to
> run RC build.
>
> On 2021/07/19 12:47:46, Petr Ivanov wrote:
>> Hi!
>>
&
Hi!
Are you committer or PMC on Apache Ignite?
> On 19 Jul 2021, at 14:40, Alexey Gidaspov wrote:
>
> Hi, All!
>
> I've found out that I don't have enough permissions to run RC build for
> ignite-2.11 branch on TC. Can anyone help me?
y Pavlov wrote:
>>>
>>> Hi Petr,
>>>
>>> Sad news, but anyway, thank you for letting community know.
>>>
>>> Sincerely,
>>> Dmitriy Pavlov
>>>
>>> On 2021/06/21 16:19:16, Petr Ivanov wrote:
>>>> Hi, Igniters!
;
> On 2021/06/21 16:19:16, Petr Ivanov wrote:
>> Hi, Igniters!
>>
>>
>> Currently our TC instance is out of order due to power outage (power booth
>> burned down).
>> Restoration can take 1-2 days at least.
>>
>> I will keep you updated on further news. Please, stand by.
Hi, Igniters!
Currently our TC instance is out of order due to power outage (power booth
burned down).
Restoration can take 1-2 days at least.
I will keep you updated on further news. Please, stand by.
Hi, Aleksey.
What do you mean by "manage"?
> On 9 Jun 2021, at 12:42, Alexey Gidaspov wrote:
>
> Hi, All!
>
> I've found out that I can't manage builds at Team City. Can anyone tell me
> how can I get necessary access rights? My TC account name is agidaspov.
earlier maven versions. Why we should trust this patch
> (moreover, it breaks even some travis ci checks)
>
> пн, 24 мая 2021 г. в 10:09, Petr Ivanov :
>>
>> Our TeamCity currently does not support 3.8.1 maven build runner.
>> I think it will be available with 2021
ithub/apache/ignite/jobs/506675544 should be at
> least fixed
>
> пт, 21 мая 2021 г. в 10:22, Petr Ivanov :
>>
>> Hi, Ilya.
>>
>>
>> Left small comment on formatting issue.
>> Otherwise looks good!
>>
>>
>> Considering
Hi, Ilya.
Left small comment on formatting issue.
Otherwise looks good!
Considering 3.8.1 maven support — we will be migrating builds there after TC
2021.1 will be delivered.
> On 20 May 2021, at 19:22, Ilya Korol wrote:
>
> Hi, all.
>
> Maybe someone has already faced the issue with
Mutes remove themselves when test is successful again.
Or you are referring to overall list of mutes on test project?
> On 20 May 2021, at 11:27, aonikolaev wrote:
>
> Hi Igniters,
> I want to start dealing with muted and ignored tests on the TC bot that have
> lost relevance or require
t; Module names in settings of the suite [1] should be changed.
>
> [1]
> https://ci.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_OldRunAllTests?mode=builds#all-projects
>
> чт, 22 апр. 2021 г. в 11:49, Petr Ivanov :
>
>>
>> Looks good.
>>
ms to be in too early stage for packaging, IMHO.
> We see very few interest in improving Apache Ignite 2.x packages, anyway.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 24 февр. 2021 г. в 19:01, Petr Ivanov :
>
>> Hi, Igniters.
>>
>>
>>
t;>>
>>> The release script has this issue too. It will work fine with that name.
>>>
>>> ср, 21 апр. 2021 г. в 10:37, Petr Ivanov :
>>>>
>>>> I checked the modules and there is misnaming issue which I think is
>>>> critical
I checked the modules and there is misnaming issue which I think is critical to
test integration automation on TC.
Can we change maven module names sping-data-2.x-ext to align with directory
name? Currently there is underscore in maven module name, which is hyphen in
directory name.
> On 21
Maksim,
Great summary!
+1 for versioning scheme.
However, deprecation rules can be possibly misleading.
I think that we should use 'since' as a mandatory annotation, that will mark
the release where the API can (not should) be changed, regardless of our
intention to modify it.
And add some
- MAVEN_CHECKS, default
>>>>> value is
>>>>>>> "-Plicenses,checkstyle,check-licenses,check-test-suites".
>>>>>>> 2. Use it in a command along with MAVEN_MODULES_STRING.
>>>>>>> -U -Pall-java,all-scala,scala,lgpl,e
If profile can handle this — its ok.
For choosing build type — we can introduce select, that will choose between -p
and -DskipTests=true (defaulting to profile).
Thus [Build] will pass either way.
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911) 945-0
rue. I'd propose to
> change it to the profile "skip-docs", that was introduced in ticket [1]
> IGNITE-13623. As the setting "maven.javadoc.skip" does not affect scaladocs.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13623
> <https://issues.apache.org/
Won't the absence of -DskipTests flag trigger ALL the tests for all modules?
This flag was added intentionally.
Instead, I'd put Non-Suited tests into some kind of sanity check, group all
sanity checks in single Run All, and make tests depend on it's successful pass.
Regards,
Petr Ivanov
Head
I'm sorry, I forgot to write on dev-list about this agent.
Indeed the target files were removed manually.
> On 24 Feb 2021, at 19:32, Max Timonin wrote:
>
> Looks like somebody fixed that. An hour ago Build succeeded at last [1]. It
> was the first successful job for a long time. Thanks!
>
>
Hi, Igniters.
Sincerely asking you to help me with testing new RPM package for apache ignite
3.x [1]
Currently what is needed to be tested — successful installation and binary run
under most of RHEL based distributions: Red Hat, CentOS, Oracle Linux, Fedora,
etc.
Any other thoughts and
of merged PRs and protecting the main branch make sense.
>
>> On 20 Feb 2021, at 18:30, Pavel Tupitsyn wrote:
>>
>> +1
>>
>> - Close inactive PRs (1 month or so?)
>> - Enable main branch protection (no force pushes, require linear history,
>> requir
Hi, Igniters!
When we started Ignite 3.x in new repository, not only we have received a
chance to cleanup codebase, but to maintain some order in development tools,
like GitHub.
Currently in 2.x repository we have lots of stalled PRs and branches, which not
only clog the repository, but also
e.html?buildTypeId=IgniteExtensions_Tests_SpringTransactions_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv
>
> On 10.02.2021 11:39, Petr Ivanov wrote:
>> Very good, thanks!
>> I will prepare build shortly.
>>
>> About flakiness — send me link to build where problem is, I will try to
>> investigate.
&
e.
>>> [22:47:43]The syntax of the command is incorrect.
>>> [22:47:43]'cp' is not recognized as an internal or external command,
>>> [22:47:43]operable program or batch file.
>>> [22:47:43]Process exited with code 1/
>>>
>>>
>>> Cou
ease?
>
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-14150
>
> [2] -
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteExtensions_Tests_Flink_IgniteExtensions_Tests=%3Cdefault%3E=buildTypeStatusDiv
>
> On 09.02.2021 13:36, Petr Ivanov wrot
As much as I understood — we execute internal class as plugin, where all the
magic is done.
Seems pretty solid in Maven part. Java part, unfortunately, cannot check.
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911) 945-00-59
> On 9 Feb 2021, a
Hi, Ilya.
I've added Inspections to Run All.
Checkstyle is currently integrated to Build and can be deleted.
Where can I find the code for check-test-suites profile?
Regards,
Petr Ivanov
Head of IT
IT & Development Solutions | GRIDGAIN SYSTEMS
+7 (911) 945-00-59
> On 9 Feb 2021, a
Hi, Nikolay.
I've created a set of tests for extensions, and part of them are failing with:
JUnit4Provider.invoke:159->executeTestSet:238->executeWithRerun:273->execute:365
» NoSuchMethod
java.lang.NoSuchMethodError:
Thanks for checking this out, Mikhail.
I will add other suites with the same setup later this week.
> On 8 Feb 2021, at 11:42, Mikhail Petrov wrote:
>
> Petr,
>
>
> It works. Thank you very much.
>
> On 05.02.2021 14:49, Petr Ivanov wrote:
>> Mikhail,
>>
ensions/pull/33
>
> On 05.02.2021 12:35, Petr Ivanov wrote:
>> Hi, Mikhail.
>>
>> Is there a PR with you extension, so I can test TC build configuration?
>>
>>
>>> On 28 Jan 2021, at 19:03, Petr Ivanov wrote:
>>>
>>> It seems that we need ful
Hi, Mikhail.
Is there a PR with you extension, so I can test TC build configuration?
> On 28 Jan 2021, at 19:03, Petr Ivanov wrote:
>
> It seems that we need full set of tests for extensions.
>
> I will refactor that project in couple of days and add suite for your
d change its parameters [1] to add a new module and test-suite.
>
> It turned out that build configuration parameters can be overridden for each
> particular build without additional permissions or copying something.
>
> Sorry for bothering you.
>
> On 28.01.2021 16:17,
1 - 100 of 397 matches
Mail list logo
