[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400205#comment-17400205
]
Peter Ivanov commented on IGNITE-14740:
---
See:
https://ci.ignite.apache.org/buildConfiguration/DevAi2x_Test_2/6138093?buildTab=log=3=20
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17400200#comment-17400200
]
Peter Ivanov commented on IGNITE-14740:
---
You should not try to install python, rather use {{pyenv version}} to choose
already installed.
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399966#comment-17399966
]
Peter Ivanov commented on IGNITE-14740:
---
For now, you should add
{code:bash}
export PYENV_ROOT="/opt/pyenv"
export PATH="${PYENV_ROOT}/bin:${PATH}"
eval "$(pyenv init - --no-rehash)"
eval "$(pyenv virtualenv-init -)"
{code}
before executing pyenv.
I am searching for the way to update agents without redeployment.
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399724#comment-17399724
]
Peter Ivanov commented on IGNITE-14740:
---
[~ivandasch], can you check the installation of {{pyenv}} and Pythons on
{{aitc-lin01_01}} agent, please?
{code:bash}
teamcity@866d67a5d073:$ pyenv versions
* system (set by /opt/pyenv/version)
3.6.14
3.7.11
3.8.11
3.9.6
{code}
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399720#comment-17399720
]
Peter Ivanov edited comment on IGNITE-14740 at 8/16/21, 12:25 PM:
--
Installation instructions:
# Install software (Ubuntu):
{code:bash}
apt update && \
apt install -y --no-install-recommends libbz2-dev libreadline-dev
{code}
# Add to {{/etc/bash.bashrc}}
{code:bash}
export PYENV_ROOT="/opt/pyenv"
export PATH="${PYENV_ROOT}/bin:${PATH}"
eval "$(pyenv init --no-rehash)"
eval "$(pyenv virtualenv-init -)"
{code}
# Install {{pyenv:}}
{code:bash}
curl https://pyenv.run | bash
git clone https://github.com/momo-lab/pyenv-install-latest.git "$(pyenv
root)"/plugins/pyenv-install-latest
{code}
# Install required version of python:
{code:bash}
pyenv install-latest 3.
{code}
was (Author: vveider):
Installation instructions:
# Install software (Ubuntu):
{code:java}
apt update && \
apt install -y --no-install-recommends libbz2-dev libreadline-dev{code}
# {{Add to /etc/bash.bashrc}}
{code:java}
export PYENV_ROOT="/opt/pyenv"
export PATH="${PYENV_ROOT}/bin:${PATH}"
eval "$(pyenv init --no-rehash)"
eval "$(pyenv virtualenv-init -)"{code}
# {{Install pyenv:}}
{code:java}
curl https://pyenv.run | bash
{code}
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17399720#comment-17399720
]
Peter Ivanov commented on IGNITE-14740:
---
Installation instructions:
# Install software (Ubuntu):
{code:java}
apt update && \
apt install -y --no-install-recommends libbz2-dev libreadline-dev{code}
# {{Add to /etc/bash.bashrc}}
{code:java}
export PYENV_ROOT="/opt/pyenv"
export PATH="${PYENV_ROOT}/bin:${PATH}"
eval "$(pyenv init --no-rehash)"
eval "$(pyenv virtualenv-init -)"{code}
# {{Install pyenv:}}
{code:java}
curl https://pyenv.run | bash
{code}
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14016) Prepare an RPM package for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14016: -- Attachment: (was: apache-ignite-3.0.0-1.noarch.rpm) > Prepare an RPM package for Ignite 3.0 > - > > Key: IGNITE-14016 > URL: https://issues.apache.org/jira/browse/IGNITE-14016 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Attachments: rhel.log > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15304) Validate POM files for duplicate dependencies
[
https://issues.apache.org/jira/browse/IGNITE-15304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-15304:
-
Assignee: Peter Ivanov
> Validate POM files for duplicate dependencies
> -
>
> Key: IGNITE-15304
> URL: https://issues.apache.org/jira/browse/IGNITE-15304
> Project: Ignite
> Issue Type: Bug
>Reporter: Semyon Danilov
>Assignee: Peter Ivanov
>Priority: Major
> Labels: ignite-3
>
> {code:java}
> Some problems were encountered while building the effective model for
> org.apache.ignite:ignite-raft:jar:3.0.0-SNAPSHOT
> 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be
> unique: org.apache.ignite:ignite-core:test-jar -> duplicate declaration of
> version (?) @ line 119, column 21
> It is highly recommended to fix these problems because they threaten the
> stability of your build.
> For this reason, future Maven versions might no longer support building such
> malformed projects.{code}
> It seems that we've encountered duplicate dependency declarations. Such
> misconfiguration threatens the stability of a build, so it should be
> eliminated before the merge. I propose adding dependency:analyze-duplicate to
> the sanity checks phase
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-15303) Maven Sanity Check is broken in main branch
[ https://issues.apache.org/jira/browse/IGNITE-15303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-15303: - Assignee: Peter Ivanov > Maven Sanity Check is broken in main branch > --- > > Key: IGNITE-15303 > URL: https://issues.apache.org/jira/browse/IGNITE-15303 > Project: Ignite > Issue Type: Bug >Reporter: Ivan Bessonov >Assignee: Peter Ivanov >Priority: Blocker > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > > https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven?branch=%3Cdefault%3E=overview=builds -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15025) Add Maven check scripts to VCS
[ https://issues.apache.org/jira/browse/IGNITE-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17398023#comment-17398023 ] Peter Ivanov commented on IGNITE-15025: --- [~amashenkov], I've updated script with all comments you've provided. Please, check. > Add Maven check scripts to VCS > -- > > Key: IGNITE-15025 > URL: https://issues.apache.org/jira/browse/IGNITE-15025 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 2h 20m > Remaining Estimate: 0h > > Currently, only TC has scripts for Maven checks which leads to several > problems: > # Developers can't use them to check code locally > # Scripts can be lost with TC in inaccurate configuration operation. > It is required to move scripts to Ignite's codebase and call them from TC > build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17392281#comment-17392281 ] Peter Ivanov commented on IGNITE-14017: --- [~vibhuti_sawant], nope. All other images will be added in https://issues.apache.org/jira/browse/IGNITE-15209 > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Labels: docker > Fix For: 2.12 > > Attachments: Dockerfile > > Time Spent: 40m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15209) Add additional docker images.
[ https://issues.apache.org/jira/browse/IGNITE-15209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-15209: - Assignee: Peter Ivanov > Add additional docker images. > - > > Key: IGNITE-15209 > URL: https://issues.apache.org/jira/browse/IGNITE-15209 > Project: Ignite > Issue Type: New Feature >Reporter: Andrey Mashenkov >Assignee: Peter Ivanov >Priority: Minor > Labels: docker, newbie > > We have docker images for x86-64 on JDK 8 and s390x on JDK 11. > Let's add images for x86-64 on JDK 11 and for s390x on JDK 8 for better UX. > This will cost us almost nothing but may be useful. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-15025) Add Maven check scripts to VCS
[ https://issues.apache.org/jira/browse/IGNITE-15025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-15025: -- Description: Currently, only TC has scripts for Maven checks which leads to several problems: # Developers can't use them to check code locally # Scripts can be lost with TC in inaccurate configuration operation. It is required to move scripts to Ignite's codebase and call them from TC build. was: Currently, only TC has scripts for Maven checks which leads to several problems: # Developers can use them to check code locally # Scripts can be lost with TC in inaccurate configuration operation. It is required to move scripts to Ignite's codebase and call them from TC build. > Add Maven check scripts to VCS > -- > > Key: IGNITE-15025 > URL: https://issues.apache.org/jira/browse/IGNITE-15025 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, only TC has scripts for Maven checks which leads to several > problems: > # Developers can't use them to check code locally > # Scripts can be lost with TC in inaccurate configuration operation. > It is required to move scripts to Ignite's codebase and call them from TC > build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387406#comment-17387406 ] Peter Ivanov commented on IGNITE-14017: --- [~imurchenko], please review the PR. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.12 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17387405#comment-17387405 ] Peter Ivanov commented on IGNITE-14017: --- [~vibhuti_sawant], sorry for delay. I've updated PR with your Dockerfile + my additions to better comply with best practices on Dockerfile composition. Please, check that it is working as you expect. Afterwards if everything is OK – we will look for committer to merge changes. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.12 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-15168) Investigate local dependency purge for always clean build
[ https://issues.apache.org/jira/browse/IGNITE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386096#comment-17386096 ] Peter Ivanov edited comment on IGNITE-15168 at 7/23/21, 8:56 AM: - Visa: https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_RunAllTests/6099708 was (Author: vveider): Tests > Investigate local dependency purge for always clean build > - > > Key: IGNITE-15168 > URL: https://issues.apache.org/jira/browse/IGNITE-15168 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > This plugin > [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] > can remove internal module dependency artifacts from local repository in > order to use local resolution scope each time the project is being built, > thus, providing clean build without additional artifacts resolution or > downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15168) Investigate local dependency purge for always clean build
[ https://issues.apache.org/jira/browse/IGNITE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17386096#comment-17386096 ] Peter Ivanov commented on IGNITE-15168: --- Tests > Investigate local dependency purge for always clean build > - > > Key: IGNITE-15168 > URL: https://issues.apache.org/jira/browse/IGNITE-15168 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > Time Spent: 20m > Remaining Estimate: 0h > > This plugin > [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] > can remove internal module dependency artifacts from local repository in > order to use local resolution scope each time the project is being built, > thus, providing clean build without additional artifacts resolution or > downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15168) Investigate local dependency purge for always clean build
[ https://issues.apache.org/jira/browse/IGNITE-15168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-15168: - Assignee: Peter Ivanov > Investigate local dependency purge for always clean build > - > > Key: IGNITE-15168 > URL: https://issues.apache.org/jira/browse/IGNITE-15168 > Project: Ignite > Issue Type: Improvement >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Fix For: 3.0.0-alpha3 > > > This plugin > [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] > can remove internal module dependency artifacts from local repository in > order to use local resolution scope each time the project is being built, > thus, providing clean build without additional artifacts resolution or > downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15168) Investigate local dependency purge for always clean build
Peter Ivanov created IGNITE-15168: - Summary: Investigate local dependency purge for always clean build Key: IGNITE-15168 URL: https://issues.apache.org/jira/browse/IGNITE-15168 Project: Ignite Issue Type: Improvement Reporter: Peter Ivanov Fix For: 3.0.0-alpha3 This plugin [https://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html] can remove internal module dependency artifacts from local repository in order to use local resolution scope each time the project is being built, thus, providing clean build without additional artifacts resolution or downloading. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15165) Fix maven build when maven.test.skip is set
[ https://issues.apache.org/jira/browse/IGNITE-15165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17384737#comment-17384737 ] Peter Ivanov commented on IGNITE-15165: --- Looks good, please, proceed with merge. > Fix maven build when maven.test.skip is set > --- > > Key: IGNITE-15165 > URL: https://issues.apache.org/jira/browse/IGNITE-15165 > Project: Ignite > Issue Type: Bug >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > `mvn clean install -DskipTests -Dmaven.test.skip=true` has stopped working > after IGNITE-14983 because ignite-network both depends on a test-jar of the > ignite-core module and builds its own test-jar. This leads to maven requiring > a test scope resolution which is not possible due to the fact that test-jars > are not actually getting built with maven.test.skip set to true -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14591) Add Javadoc rules to maven checkstyle plugin.
[
https://issues.apache.org/jira/browse/IGNITE-14591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383376#comment-17383376
]
Peter Ivanov commented on IGNITE-14591:
---
TC suite updated and checked.
Changes looks good, please, proceed with merge, thanks!
> Add Javadoc rules to maven checkstyle plugin.
> -
>
> Key: IGNITE-14591
> URL: https://issues.apache.org/jira/browse/IGNITE-14591
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Andrey Mashenkov
>Priority: Major
> Labels: ignite-3
> Time Spent: 1h
> Remaining Estimate: 0h
>
> h3. Motivation.
> For now, we have a Javadoc suite on TC which runs {{javadoc}} tool as it is
> done for releases for javadoc generation purposes.
> Using this tool helps us to detect a markup error in the resulting HTML code
> at the early stage.
> However, it treats style violations as just a WARNING which never make the TC
> task failed.
> We tried to use an additional check (actually a log parsing) to fail the TC
> task, but now it is disabled because we can't perform the same checks on the
> user side.
> Also, style checks are not configurable, so using the {{javadoc}} tool for
> that purpose looks useless.
> h3. Descrition.
> Checkstyle plugin has a module that performs style checks for javadocs and
> its configuration looks flexible enough.
> In opposite to {{javadoc}} tool, checkstyle plugin fails the maven task in
> case of style violation as on TC as on user side.
> Let's
> * leave current Javadoc TC suite ({{javadoc}} tool) as is with suppressing
> styles warnings.
> * add javadoc rules to maven-checkstyle-plugin and update the Codestyle guide.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15137) Fix javadoc phase for ignite-cli module
[
https://issues.apache.org/jira/browse/IGNITE-15137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17383278#comment-17383278
]
Peter Ivanov commented on IGNITE-15137:
---
{{javadoc:aggregate}} fix looks good to me. Please, proceed with merge.
> Fix javadoc phase for ignite-cli module
> ---
>
> Key: IGNITE-15137
> URL: https://issues.apache.org/jira/browse/IGNITE-15137
> Project: Ignite
> Issue Type: Bug
>Reporter: Semyon Danilov
>Assignee: Semyon Danilov
>Priority: Major
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15144) Missing @return in Javadoc for LoggerMessageHelper#arrayFormat()
Peter Ivanov created IGNITE-15144:
-
Summary: Missing @return in Javadoc for
LoggerMessageHelper#arrayFormat()
Key: IGNITE-15144
URL: https://issues.apache.org/jira/browse/IGNITE-15144
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha3
Reporter: Peter Ivanov
Assignee: Vladislav Pyatkov
Fix For: 3.0.0-alpha3
{{mvn install -P javadoc -Dmaven.test.skip}}:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:3.2.0:jar (default) on project
ignite-core: MavenReportException: Error while generating Javadoc:
[ERROR] Exit code: 1 - javadoc: error - Error fetching URL:
https://ignite.apache.org/releases/latest/javadoc/
[ERROR]
/Users/vveider/Development/ignite-3/modules/core/src/main/java/org/apache/ignite/lang/LoggerMessageHelper.java:94:
warning: no @return
[ERROR] static String arrayFormat(final String messagePattern, final
Object[] params) {
[ERROR] ^
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/jdk-11.0.1.jdk/Contents/Home/bin/javadoc
@options @argfile
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/Users/vveider/Development/ignite-3/modules/core/target/apidocs' dir.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15025) Add Maven check scripts to VCS
Peter Ivanov created IGNITE-15025: - Summary: Add Maven check scripts to VCS Key: IGNITE-15025 URL: https://issues.apache.org/jira/browse/IGNITE-15025 Project: Ignite Issue Type: Improvement Reporter: Peter Ivanov Assignee: Peter Ivanov Currently, only TC has scripts for Maven checks which leads to several problems: # Developers can use them to check code locally # Scripts can be lost with TC in inaccurate configuration operation. It is required to move scripts to Ignite's codebase and call them from TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-15021) Apache Rat plugin does not check full text license
[ https://issues.apache.org/jira/browse/IGNITE-15021?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-15021: - Assignee: Ivan Bessonov (was: Peter Ivanov) > Apache Rat plugin does not check full text license > -- > > Key: IGNITE-15021 > URL: https://issues.apache.org/jira/browse/IGNITE-15021 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Ivan Bessonov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha3 > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, Apache Rat plugin configuration matches not full text of license > from settings, but overall AL2.0 license header. Thus, some files missed > check. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15021) Apache Rat plugin does not check full text license
Peter Ivanov created IGNITE-15021: - Summary: Apache Rat plugin does not check full text license Key: IGNITE-15021 URL: https://issues.apache.org/jira/browse/IGNITE-15021 Project: Ignite Issue Type: Bug Reporter: Peter Ivanov Assignee: Peter Ivanov Currently, Apache Rat plugin configuration matches not full text of license from settings, but overall AL2.0 license header. Thus, some files missed check. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14120) select count * returns multiple rows
[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-14120: - Assignee: Vladimir Ermakov (was: Peter Ivanov) > select count * returns multiple rows > > > Key: IGNITE-14120 > URL: https://issues.apache.org/jira/browse/IGNITE-14120 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8.1 >Reporter: Isaac Zhu >Assignee: Vladimir Ermakov >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > I have a partitioned table which has 1 backup, the *queryParallelism* is set > to 4. > The table primary key is column "ID", > If I do this query: > select count( * ) from my_table where ID = 1000; > It will return 4 rows: > 1 > 0 > 0 > 0 > > If I query by other not primary-key columns of this table, the result is > good, like: > select count( *) from my_table where name = 'abcd' > result is: > 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14120) select count * returns multiple rows
[ https://issues.apache.org/jira/browse/IGNITE-14120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-14120: - Assignee: Peter Ivanov (was: Vladimir Ermakov) > select count * returns multiple rows > > > Key: IGNITE-14120 > URL: https://issues.apache.org/jira/browse/IGNITE-14120 > Project: Ignite > Issue Type: Bug > Components: sql >Affects Versions: 2.8.1 >Reporter: Isaac Zhu >Assignee: Peter Ivanov >Priority: Major > Time Spent: 1h 50m > Remaining Estimate: 0h > > I have a partitioned table which has 1 backup, the *queryParallelism* is set > to 4. > The table primary key is column "ID", > If I do this query: > select count( * ) from my_table where ID = 1000; > It will return 4 rows: > 1 > 0 > 0 > 0 > > If I query by other not primary-key columns of this table, the result is > good, like: > select count( *) from my_table where name = 'abcd' > result is: > 0 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17355071#comment-17355071 ] Peter Ivanov commented on IGNITE-14017: --- Hi! I've seen the attachment, thanks! I will attend to issue later this week. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Attachments: Dockerfile > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351766#comment-17351766 ] Peter Ivanov edited comment on IGNITE-14017 at 5/26/21, 1:14 PM: - You can just attach new Dockerfile, or patch file with changes to current. Concerning Docker release — you have to raise discussion on Apache Ignite dev-list about necessity of including s390x Docker to release. I guess this time (nearest release 2.11) you can ping me directly about releasing s390x — I will check how it can be done in terms of tags and repositories. was (Author: vveider): You can just attach new Dockerfile, or patch file with changes to current. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351766#comment-17351766 ] Peter Ivanov commented on IGNITE-14017: --- You can just attach new Dockerfile, or patch file with changes to current. > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Time Spent: 20m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[
https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17351053#comment-17351053
]
Peter Ivanov commented on IGNITE-14017:
---
Concerning proposed hierarchy, I would move ordinary Docker build files to
{{deliveries/docker/apache-ignite/x64}} instead
{{deliveries/docker/apache-ignite}}.
Other comments are in PR — if some of them are not clear, I can propose patch
with changes.
Also, I am no committer and would not be able to merge PR anyway ¯\_(ツ)_/¯.
> Willing to add s390x support to the docker image.
> -
>
> Key: IGNITE-14017
> URL: https://issues.apache.org/jira/browse/IGNITE-14017
> Project: Ignite
> Issue Type: New Feature
>Reporter: Prajakta Chaudhari
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We are willing to add s390x support to the docker image. Dockerfile provided
> on Apache Ignite GitHub repository
> (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is
> working fine on s390x architecture. However we could not get any information
> about how does the docker image build and release process work. Can you
> please give some pointers to go ahead with the task?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14772) After test-jar dependency added, pmd check with compile only no longer works
[ https://issues.apache.org/jira/browse/IGNITE-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14772: -- Fix Version/s: 3.0.0-alpha2 > After test-jar dependency added, pmd check with compile only no longer works > > > Key: IGNITE-14772 > URL: https://issues.apache.org/jira/browse/IGNITE-14772 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 3.0.0-alpha2 > > > After > https://github.com/apache/ignite-3/commit/9f3e0282a17ed21e14e7079f243bb5f7dcd86dba > pmd check with compile only no longer works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14772) After test-jar dependency added, pmd check with compile only no longer works
[ https://issues.apache.org/jira/browse/IGNITE-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14772: -- Affects Version/s: 3.0.0-alpha1 > After test-jar dependency added, pmd check with compile only no longer works > > > Key: IGNITE-14772 > URL: https://issues.apache.org/jira/browse/IGNITE-14772 > Project: Ignite > Issue Type: Bug >Affects Versions: 3.0.0-alpha1 >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 3.0.0-alpha2 > > > After > https://github.com/apache/ignite-3/commit/9f3e0282a17ed21e14e7079f243bb5f7dcd86dba > pmd check with compile only no longer works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14772) After test-jar dependency added, pmd check with compile only no longer works
[ https://issues.apache.org/jira/browse/IGNITE-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14772: -- Affects Version/s: (was: 3.0.0-alpha1) > After test-jar dependency added, pmd check with compile only no longer works > > > Key: IGNITE-14772 > URL: https://issues.apache.org/jira/browse/IGNITE-14772 > Project: Ignite > Issue Type: Bug >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Critical > Fix For: 3.0.0-alpha2 > > > After > https://github.com/apache/ignite-3/commit/9f3e0282a17ed21e14e7079f243bb5f7dcd86dba > pmd check with compile only no longer works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14772) After test-jar dependency added, pmd check with compile only no longer works
Peter Ivanov created IGNITE-14772: - Summary: After test-jar dependency added, pmd check with compile only no longer works Key: IGNITE-14772 URL: https://issues.apache.org/jira/browse/IGNITE-14772 Project: Ignite Issue Type: Bug Reporter: Peter Ivanov Assignee: Peter Ivanov After https://github.com/apache/ignite-3/commit/9f3e0282a17ed21e14e7079f243bb5f7dcd86dba pmd check with compile only no longer works. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347486#comment-17347486
]
Peter Ivanov commented on IGNITE-14740:
---
So will there be enough installing pyenv and using it to install target Python
versions on every agent?
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14738:
--
Affects Version/s: (was: python-0.4.0)
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14738:
--
Affects Version/s: python-0.4.0
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347471#comment-17347471
]
Peter Ivanov commented on IGNITE-14740:
---
That is separate task which is not related to infrastructure changes.
Configuring TC if you do not have enough permissions or knowledge should be
done in separate issue.
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347444#comment-17347444
]
Peter Ivanov edited comment on IGNITE-14738 at 5/19/21, 9:36 AM:
-
I do not know such ¯\\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
was (Author: vveider):
I do not know such ¯\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347444#comment-17347444
]
Peter Ivanov edited comment on IGNITE-14738 at 5/19/21, 9:36 AM:
-
I do not know such ¯\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
was (Author: vveider):
I do not know such ¯\\\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347444#comment-17347444
]
Peter Ivanov edited comment on IGNITE-14738 at 5/19/21, 9:36 AM:
-
I do not know such ¯\\\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
was (Author: vveider):
I do not know such ¯_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347444#comment-17347444
]
Peter Ivanov edited comment on IGNITE-14738 at 5/19/21, 9:36 AM:
-
I do not know such ¯_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
was (Author: vveider):
I do not know such ¯\\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347453#comment-17347453
]
Peter Ivanov commented on IGNITE-14740:
---
I do not understand what exactly should be done other then installing pyenv and
preinstalling target Python versions?
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347452#comment-17347452
]
Peter Ivanov commented on IGNITE-14738:
---
{{tox}} is installed on all Linux agents.
Please, check.
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14740) Add multiple python versions on TC agents for testing pyignite
[
https://issues.apache.org/jira/browse/IGNITE-14740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347447#comment-17347447
]
Peter Ivanov commented on IGNITE-14740:
---
{quote}Before invoking tox, script should invoke pyenv init --path and pyenv
shell with specific python version.{quote}
I guess that should be controlled by TC build configuration, not by internal
infrastructure, am I wrong?
> Add multiple python versions on TC agents for testing pyignite
> --
>
> Key: IGNITE-14740
> URL: https://issues.apache.org/jira/browse/IGNITE-14740
> Project: Ignite
> Issue Type: New Feature
> Components: python, thin client
>Reporter: Ivan Daschinsky
>Assignee: Peter Ivanov
>Priority: Major
> Labels: python, teamcity
>
> In order to test {{pyignite}} against different python versions, I suggests
> followings
> 1. Install [pyenv|https://github.com/pyenv/pyenv]
> 2. Install through {{pyenv}} different python versions (3.6, 3.7, 3.8, 3.9)
> Before invoking {{tox}}, script should invoke {{pyenv init --path}} and
> {{pyenv shell}} with specific python version.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347444#comment-17347444
]
Peter Ivanov commented on IGNITE-14738:
---
I do not know such ¯\_(ツ)_/¯
Just assign new issue to me and I will take it in priority pool.
Thanks!
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347437#comment-17347437
]
Peter Ivanov commented on IGNITE-14738:
---
pyenv installation currently requires agent redesign in terms of provided
versions of Python.
I will need some time for research.
Please, file separate ticket for this issue.
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14738) Remove pytest-runner dependency from setup.py
[
https://issues.apache.org/jira/browse/IGNITE-14738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17347318#comment-17347318
]
Peter Ivanov commented on IGNITE-14738:
---
[~ivandasch] — how to install this package?
{code}
pip install tox
{code} ?
> Remove pytest-runner dependency from setup.py
> -
>
> Key: IGNITE-14738
> URL: https://issues.apache.org/jira/browse/IGNITE-14738
> Project: Ignite
> Issue Type: Improvement
> Components: python, thin client
>Affects Versions: python-0.4.0
>Reporter: Ivan Daschinsky
>Assignee: Ivan Daschinsky
>Priority: Major
> Labels: python, thin
>
> This dependency should be removed
> 1. It is deprecated (see https://pypi.org/project/pytest-runner/)
> 2. We already adopted {{tox}} and use it in travis-ci
> 3. It cause some issues when trying to install source package from local pypi
> mirror ({{pytest-runner}} should be installed separately before
> {{pyignite}}). However, when installing directly from pypi.org, all works ok.
> But, unfortunatelly, our TC agents doesn't have {{tox}} installed
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14735) Fix CheckStyle report not being generated in case of violation
Peter Ivanov created IGNITE-14735: - Summary: Fix CheckStyle report not being generated in case of violation Key: IGNITE-14735 URL: https://issues.apache.org/jira/browse/IGNITE-14735 Project: Ignite Issue Type: Bug Reporter: Peter Ivanov Assignee: Peter Ivanov If CheckStyle plugin detects violation, it does not generate HTML report. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-14656) Modules in root pom.xml must be lexicographically sorted.
[
https://issues.apache.org/jira/browse/IGNITE-14656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333087#comment-17333087
]
Peter Ivanov edited comment on IGNITE-14656 at 4/27/21, 10:13 AM:
--
Added check step.
Checked on
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven/5983708
was (Author: vveider):
Added check step:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven/5983688
> Modules in root pom.xml must be lexicographically sorted.
> -
>
> Key: IGNITE-14656
> URL: https://issues.apache.org/jira/browse/IGNITE-14656
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha1
>Reporter: Ivan Bessonov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In order to make project more clean we should enforce sorting of
> {{}} section in root {{pom.xml}} file.
> Right now order is already broken by the last two entities - {{baseline}} and
> {{affinity}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14656) Modules in root pom.xml must be lexicographically sorted.
[
https://issues.apache.org/jira/browse/IGNITE-14656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14656:
--
Fix Version/s: 3.0.0-alpha2
> Modules in root pom.xml must be lexicographically sorted.
> -
>
> Key: IGNITE-14656
> URL: https://issues.apache.org/jira/browse/IGNITE-14656
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha1
>Reporter: Ivan Bessonov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
>
> In order to make project more clean we should enforce sorting of
> {{}} section in root {{pom.xml}} file.
> Right now order is already broken by the last two entities - {{baseline}} and
> {{affinity}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14656) Modules in root pom.xml must be lexicographically sorted.
[
https://issues.apache.org/jira/browse/IGNITE-14656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17333087#comment-17333087
]
Peter Ivanov commented on IGNITE-14656:
---
Added check step:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven/5983688
> Modules in root pom.xml must be lexicographically sorted.
> -
>
> Key: IGNITE-14656
> URL: https://issues.apache.org/jira/browse/IGNITE-14656
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha1
>Reporter: Ivan Bessonov
>Assignee: Peter Ivanov
>Priority: Major
>
> In order to make project more clean we should enforce sorting of
> {{}} section in root {{pom.xml}} file.
> Right now order is already broken by the last two entities - {{baseline}} and
> {{affinity}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14656) Modules in root pom.xml must be lexicographically sorted.
[
https://issues.apache.org/jira/browse/IGNITE-14656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-14656:
-
Assignee: Peter Ivanov
> Modules in root pom.xml must be lexicographically sorted.
> -
>
> Key: IGNITE-14656
> URL: https://issues.apache.org/jira/browse/IGNITE-14656
> Project: Ignite
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha1
>Reporter: Ivan Bessonov
>Assignee: Peter Ivanov
>Priority: Major
>
> In order to make project more clean we should enforce sorting of
> {{}} section in root {{pom.xml}} file.
> Right now order is already broken by the last two entities - {{baseline}} and
> {{affinity}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14650) Remove Apache Ignite binary from maven artifacts
[
https://issues.apache.org/jira/browse/IGNITE-14650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17331544#comment-17331544
]
Peter Ivanov commented on IGNITE-14650:
---
Checked on release build:
https://ci.ignite.apache.org/buildConfiguration/ignite3_Release_Build_BinariesMaven/5981497?buildTab=artifacts
> Remove Apache Ignite binary from maven artifacts
>
>
> Key: IGNITE-14650
> URL: https://issues.apache.org/jira/browse/IGNITE-14650
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha2
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{apache-ignite-.zip}} artifact is being deployed to maven staging /
> repositories during maven build with install / deploy commands. That is
> excess, because this artifact is being manually provided by TC.
> It is required to remove it from deployment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14650) Remove Apache Ignite binary from maven artifacts
Peter Ivanov created IGNITE-14650:
-
Summary: Remove Apache Ignite binary from maven artifacts
Key: IGNITE-14650
URL: https://issues.apache.org/jira/browse/IGNITE-14650
Project: Ignite
Issue Type: Bug
Affects Versions: 3.0.0-alpha2
Reporter: Peter Ivanov
Assignee: Peter Ivanov
Fix For: 3.0.0-alpha2
{{apache-ignite-.zip}} artifact is being deployed to maven staging /
repositories during maven build with install / deploy commands. That is excess,
because this artifact is being manually provided by TC.
It is required to remove it from deployment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14630) Fix excess versions declaration in POMs
Peter Ivanov created IGNITE-14630: - Summary: Fix excess versions declaration in POMs Key: IGNITE-14630 URL: https://issues.apache.org/jira/browse/IGNITE-14630 Project: Ignite Issue Type: Bug Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 3.0.0-alpha2 https://ci.ignite.apache.org/buildConfiguration/ignite3_Test_SanityChecks_Maven/5978039 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14558) Add information about javadoc validation and generation commands to DEVNOTES.md
[
https://issues.apache.org/jira/browse/IGNITE-14558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17325065#comment-17325065
]
Peter Ivanov commented on IGNITE-14558:
---
${current.year} is not used when checking Javadoc for correctness.
> Add information about javadoc validation and generation commands to
> DEVNOTES.md
>
>
> Key: IGNITE-14558
> URL: https://issues.apache.org/jira/browse/IGNITE-14558
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Peter Ivanov
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/IGNITE-13751 is implemented and merged
> but DEVNOTES.md is not updated.
> Information about javadoc validation and generation commands should be added
> to DEVNOTES.md.
> Also, there is unresolved variable:
> {code:java}
> ${current.year} Copyright © Apache Software Foundation
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14558) Add information about javadoc validation and generation commands to DEVNOTES.md
[
https://issues.apache.org/jira/browse/IGNITE-14558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14558:
--
Description:
https://issues.apache.org/jira/browse/IGNITE-13751 is implemented and merged
but DEVNOTES.md is not updated.
Information about javadoc validation and generation commands should be added to
DEVNOTES.md.
Also, there is unresolved variable:
{code:java}
${current.year} Copyright © Apache Software Foundation
{code}
was:
https://issues.apache.org/jira/browse/IGNITE-13751 is implemented and merged
but DEVNOTES.md is not updated.
Information about javadoc validation and generation commands should be added to
DEVNOTES.md.
Maven javadoc plugin should fail build if any 'warning' found. However, no
'errors' means javadoc is valid (well-structured), there still may be a
'warning' that means javadoc is incomplete.
Plugin option to force failure on warnings.
{code:java}
true{code}
> Add information about javadoc validation and generation commands to
> DEVNOTES.md
>
>
> Key: IGNITE-14558
> URL: https://issues.apache.org/jira/browse/IGNITE-14558
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey N. Gura
>Assignee: Peter Ivanov
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
>
> https://issues.apache.org/jira/browse/IGNITE-13751 is implemented and merged
> but DEVNOTES.md is not updated.
> Information about javadoc validation and generation commands should be added
> to DEVNOTES.md.
> Also, there is unresolved variable:
> {code:java}
> ${current.year} Copyright © Apache Software Foundation
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14558) Add information about javadoc validation and generation commands to DEVNOTES.md
[ https://issues.apache.org/jira/browse/IGNITE-14558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-14558: - Assignee: Peter Ivanov (was: Andrey Mashenkov) > Add information about javadoc validation and generation commands to > DEVNOTES.md > > > Key: IGNITE-14558 > URL: https://issues.apache.org/jira/browse/IGNITE-14558 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey N. Gura >Assignee: Peter Ivanov >Priority: Critical > Fix For: 3.0.0-alpha2 > > > https://issues.apache.org/jira/browse/IGNITE-13751 is implemented and merged > but DEVNOTES.md is not updated. > Information about javadoc validation and generation commands should be added > to DEVNOTES.md. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-13751) Add javadoc validation to sanity check.
[
https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17322049#comment-17322049
]
Peter Ivanov commented on IGNITE-13751:
---
[Apache Ignite 3.x] / [Test] / [Sanity Checks] / Javadoc
> Add javadoc validation to sanity check.
> ---
>
> Key: IGNITE-13751
> URL: https://issues.apache.org/jira/browse/IGNITE-13751
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Peter Ivanov
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's add javadoc validation plugin for sanity checks and make it run on TC.
> We need to
> 1. validate javadocs in all the packages of all the modules (excepts
> 'bytecode') for tests purposes.
> 2. compile javadocs into javadoc.jar for all the public packages
> ('org.apache.ignite.*', but 'org.apache.ignite.internal.*') to developers can
> download docs (as well as sources) from the maven.
> 3. build a site with public javadocs for release process purposes.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Issue Comment Deleted] (IGNITE-13751) Add javadoc validation to sanity check.
[
https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-13751:
--
Comment: was deleted
(was: [Apache Ignite 3.x] / [Test] / [Sanity Checks] / Javadoc)
> Add javadoc validation to sanity check.
> ---
>
> Key: IGNITE-13751
> URL: https://issues.apache.org/jira/browse/IGNITE-13751
> Project: Ignite
> Issue Type: Improvement
>Reporter: Andrey Mashenkov
>Assignee: Peter Ivanov
>Priority: Critical
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Let's add javadoc validation plugin for sanity checks and make it run on TC.
> We need to
> 1. validate javadocs in all the packages of all the modules (excepts
> 'bytecode') for tests purposes.
> 2. compile javadocs into javadoc.jar for all the public packages
> ('org.apache.ignite.*', but 'org.apache.ignite.internal.*') to developers can
> download docs (as well as sources) from the maven.
> 3. build a site with public javadocs for release process purposes.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Slava Koptilin (was: Peter Ivanov)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Peter Ivanov (was: Slava Koptilin)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Slava Koptilin (was: Peter Ivanov)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Updated] (IGNITE-14423) Node failure caused by AssertionError: Transaction does not own lock for update
[
https://issues.apache.org/jira/browse/IGNITE-14423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14423:
--
Reviewer: Peter Ivanov (was: Vyacheslav Koptilin)
> Node failure caused by AssertionError: Transaction does not own lock for
> update
> ---
>
> Key: IGNITE-14423
> URL: https://issues.apache.org/jira/browse/IGNITE-14423
> Project: Ignite
> Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Scenario:
> 1. Start 3 servers
> 2. Start 2 clients
> 3. Start two OPTIMISTIC transactions with the same key from different client
> nodes
> 4. Transfer transactions to PREPARED STATE on primary node
> 5. Stop one client node(whose transaction changed state to PREPARED last)
>
> Error in log:
> {code:java}
> [2021-03-03
> 08:52:59,807][ERROR][sys-#499%transactions.TxRecoveryWithConcurrentRollbackTest1%][GridNearTxLocal]
> Failed completing the transaction: [commit=true, tx=GridDhtTxLocal
> [nearNodeId=29551b46-74ef-4e35-af4a-d97809cc5260,
> nearFutId=08b25a6f771-eec14fa0-02ef-46b9-97d9-0f2b7c851ddb, nearMiniId=1,
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion
> [topVer=226230774, order=1614750773047, nodeOrder=4], lb=tx,
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false,
> nearNodes=KeySetView [], dhtNodes=KeySetView [], explicitLock=false,
> super=IgniteTxLocalAdapter [completedBase=null, sndTransformedVals=false,
> depEnabled=false, txState=IgniteTxStateImpl [activeCacheIds=[1544803905],
> recovery=false, mvccEnabled=false, mvccCachingCacheIds=[], txMap=ArrayList
> [IgniteTxEntry [txKey=IgniteTxKey [key=KeyCacheObjectImpl [part=1, val=1,
> hasValBytes=true], cacheId=1544803905], val=TxEntryValueHolder
> [val=CacheObjectImpl [val=null, hasValBytes=true], op=CREATE],
> prevVal=TxEntryValueHolder [val=null, op=NOOP], oldVal=TxEntryValueHolder
> [val=null, op=NOOP], entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1,
> conflictVer=null, explicitVer=null, dhtVer=null,
> filters=CacheEntryPredicate[] [], filtersPassed=false, filtersSet=false,
> entry=GridDhtCacheEntry [rdrs=ReaderId[] [], part=1,
> super=GridDistributedCacheEntry [super=GridCacheMapEntry
> [key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true], val=null,
> ver=GridCacheVersion [topVer=226230774, order=1614750774035, nodeOrder=2],
> hash=1, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc [locs=LinkedList
> [GridCacheMvccCandidate [nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271,
> ver=GridCacheVersion [topVer=226230774, order=1614750774033, nodeOrder=2],
> threadId=364, id=5, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> reentry=null, otherNodeId=207c7f09-21a9-4b99-b631-3304a522b002,
> otherVer=GridCacheVersion [topVer=226230774, order=1614750774032,
> nodeOrder=5], mappedDhtNodes=null, mappedNearNodes=null, ownerVer=null,
> serOrder=null, key=KeyCacheObjectImpl [part=1, val=1, hasValBytes=true],
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
> prevVer=null, nextVer=null]], rmts=null]], flags=3]]], prepared=1,
> locked=false, nodeId=null, locMapped=false, expiryPlc=null,
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null,
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion
> [topVer=226230774, order=1614750774035, nodeOrder=2], writeVer=null,
> implicit=false, loc=true, threadId=686, startTime=1614750774753,
> nodeId=b1f1a8e0-e1e8-4084-b9c6-bdd2a271, isolation=READ_COMMITTED,
> concurrency=OPTIMISTIC, timeout=5000, sysInvalidate=true, sys=false, plc=2,
> commitVer=GridCacheVersion [topVer=226230774, order=1614750774035,
> nodeOrder=2], finalizing=RECOVERY_FINISH, invalidParts=null, state=UNKNOWN,
> timedOut=false, topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0],
> mvccSnapshot=null, skipCompletedVers=false, parentTx=null, duration=5048ms,
> onePhaseCommit=false], size=1
> class
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException:
> Committing a transaction has produced runtime exception
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxAdapter.heuristicException(IgniteTxAdapter.java:813)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxLocalAdapter.userCommit(IgniteTxLocalAdapter.java:969)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocalAdapter.localFinish(GridDhtTxLocalAdapter.java:794)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.localFinish(GridDhtTxLocal.java:605)
> at
>
[jira] [Assigned] (IGNITE-13751) Add javadoc validation to sanity check.
[ https://issues.apache.org/jira/browse/IGNITE-13751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-13751: - Assignee: Peter Ivanov > Add javadoc validation to sanity check. > --- > > Key: IGNITE-13751 > URL: https://issues.apache.org/jira/browse/IGNITE-13751 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Peter Ivanov >Priority: Critical > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > > Let's add javadoc validation plugin for sanity checks and make it run on TC. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14283) Create the Sanity Checks job on TC
[ https://issues.apache.org/jira/browse/IGNITE-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17314842#comment-17314842 ] Peter Ivanov commented on IGNITE-14283: --- Waiting for build configuration comparison results with current Sanity Check suites. > Create the Sanity Checks job on TC > -- > > Key: IGNITE-14283 > URL: https://issues.apache.org/jira/browse/IGNITE-14283 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Peter Ivanov >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 1. The [Build] job runs without any checks. > 2. There will be a new job [Sanity Checks], that runs all checks - > checkstyle, licenses, javadoc, check-suites. > 3. [Sanity Checks] runs in parallel with [Build]. > 4. All TC jobs with tests depend on a result of the [Sanity Checks] job. If > the check job fails then a test job won't be started. > 5. Users can disable the [Sanity Checks] job with a selector on the > Parameters tab of custom TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14283) Create the Sanity Checks job on TC
[ https://issues.apache.org/jira/browse/IGNITE-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313893#comment-17313893 ] Peter Ivanov commented on IGNITE-14283: --- Added *[Missing Tests]* to *> Build*. Check this build please: https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Build/5948836 > Create the Sanity Checks job on TC > -- > > Key: IGNITE-14283 > URL: https://issues.apache.org/jira/browse/IGNITE-14283 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Peter Ivanov >Priority: Major > > 1. The [Build] job runs without any checks. > 2. There will be a new job [Sanity Checks], that runs all checks - > checkstyle, licenses, javadoc, check-suites. > 3. [Sanity Checks] runs in parallel with [Build]. > 4. All TC jobs with tests depend on a result of the [Sanity Checks] job. If > the check job fails then a test job won't be started. > 5. Users can disable the [Sanity Checks] job with a selector on the > Parameters tab of custom TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14283) Create the Sanity Checks job on TC
[ https://issues.apache.org/jira/browse/IGNITE-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313849#comment-17313849 ] Peter Ivanov commented on IGNITE-14283: --- [~timonin.maksim] — check this setup, please: https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_Test/5948806 > Create the Sanity Checks job on TC > -- > > Key: IGNITE-14283 > URL: https://issues.apache.org/jira/browse/IGNITE-14283 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Peter Ivanov >Priority: Major > > 1. The [Build] job runs without any checks. > 2. There will be a new job [Sanity Checks], that runs all checks - > checkstyle, licenses, javadoc, check-suites. > 3. [Sanity Checks] runs in parallel with [Build]. > 4. All TC jobs with tests depend on a result of the [Sanity Checks] job. If > the check job fails then a test job won't be started. > 5. Users can disable the [Sanity Checks] job with a selector on the > Parameters tab of custom TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14283) Create the Sanity Checks job on TC
[ https://issues.apache.org/jira/browse/IGNITE-14283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313738#comment-17313738 ] Peter Ivanov commented on IGNITE-14283: --- Agreed with [~timonin.maksim] to include Sanity Check steps to Build build configuration. > Create the Sanity Checks job on TC > -- > > Key: IGNITE-14283 > URL: https://issues.apache.org/jira/browse/IGNITE-14283 > Project: Ignite > Issue Type: New Feature >Reporter: Maksim Timonin >Assignee: Peter Ivanov >Priority: Major > > 1. The [Build] job runs without any checks. > 2. There will be a new job [Sanity Checks], that runs all checks - > checkstyle, licenses, javadoc, check-suites. > 3. [Sanity Checks] runs in parallel with [Build]. > 4. All TC jobs with tests depend on a result of the [Sanity Checks] job. If > the check job fails then a test job won't be started. > 5. Users can disable the [Sanity Checks] job with a selector on the > Parameters tab of custom TC build. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14457) Update Ignite 3 binary build structure
[
https://issues.apache.org/jira/browse/IGNITE-14457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313708#comment-17313708
]
Peter Ivanov commented on IGNITE-14457:
---
Fixed tests.
BTW — is it ok to push empty README and NOTICE currently, or should I add there
some text?
> Update Ignite 3 binary build structure
> --
>
> Key: IGNITE-14457
> URL: https://issues.apache.org/jira/browse/IGNITE-14457
> Project: Ignite
> Issue Type: Task
> Components: build
>Affects Versions: 3.0.0-alpha1
>Reporter: Valentin Kulichenko
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the first alpha release, we provided binaries as separate single-file
> downloads for Unix and Windows. This approach doesn't work for two reasons:
> # Website download for the Unix binary doesn't work properly, because the
> file doesn't have an extension. This doesn't seem to have a reasonable
> solution.
> # Binaries that are downloaded from the website are required to include
> {{NOTICE}} and {{LICENSE}} files.
> See IGNITE-13978 and INFRA-21332 for more details.
> As a solution, let's switch to a ZIP file containing the following:
> * {{ignite}} (Unix CLI tool)
> * {{ignite.exe}} (Windows CLI tool)
> * {{NOTICE}}
> * {{LICENSE}}
> * {{README}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14457) Update Ignite 3 binary build structure
[
https://issues.apache.org/jira/browse/IGNITE-14457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313293#comment-17313293
]
Peter Ivanov commented on IGNITE-14457:
---
[~vkulichenko], please, check [PR|https://github.com/apache/ignite-3/pull/79]
and [zip prototype|https://a.tmp.ninja/NbUVddWe.zip] (will expire in 48 hours).
> Update Ignite 3 binary build structure
> --
>
> Key: IGNITE-14457
> URL: https://issues.apache.org/jira/browse/IGNITE-14457
> Project: Ignite
> Issue Type: Task
> Components: build
>Affects Versions: 3.0.0-alpha1
>Reporter: Valentin Kulichenko
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In the first alpha release, we provided binaries as separate single-file
> downloads for Unix and Windows. This approach doesn't work for two reasons:
> # Website download for the Unix binary doesn't work properly, because the
> file doesn't have an extension. This doesn't seem to have a reasonable
> solution.
> # Binaries that are downloaded from the website are required to include
> {{NOTICE}} and {{LICENSE}} files.
> See IGNITE-13978 and INFRA-21332 for more details.
> As a solution, let's switch to a ZIP file containing the following:
> * {{ignite}} (Unix CLI tool)
> * {{ignite.exe}} (Windows CLI tool)
> * {{NOTICE}}
> * {{LICENSE}}
> * {{README}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-14017: - Assignee: Peter Ivanov (was: Ilya Murchenko) > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Peter Ivanov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313024#comment-17313024 ] Peter Ivanov commented on IGNITE-14017: --- Sorry, Vibhuti, missed that. I will take over next week. Stand by! > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14457) Update Ignite 3 binary build structure
[
https://issues.apache.org/jira/browse/IGNITE-14457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-14457:
-
Assignee: Peter Ivanov
> Update Ignite 3 binary build structure
> --
>
> Key: IGNITE-14457
> URL: https://issues.apache.org/jira/browse/IGNITE-14457
> Project: Ignite
> Issue Type: Task
> Components: build
>Affects Versions: 3.0.0-alpha1
>Reporter: Valentin Kulichenko
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
>
> In the first alpha release, we provided binaries as separate single-file
> downloads for Unix and Windows. This approach doesn't work for two reasons:
> # Website download for the Unix binary doesn't work properly, because the
> file doesn't have an extension. This doesn't seem to have a reasonable
> solution.
> # Binaries that are downloaded from the website are required to include
> {{NOTICE}} and {{LICENSE}} files.
> See IGNITE-13978 and INFRA-21332 for more details.
> As a solution, let's switch to a ZIP file containing the following:
> * {{ignite}} (Unix CLI tool)
> * {{ignite.exe}} (Windows CLI tool)
> * {{NOTICE}}
> * {{LICENSE}}
> * {{README}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-8719: Assignee: Kirill Tkalenko (was: Peter Ivanov) > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Kirill Tkalenko >Priority: Critical > Attachments: IndexRebuildAfterNodeCrashTest.java, > IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-8719) Index left partially built if a node crashes during index create or rebuild
[ https://issues.apache.org/jira/browse/IGNITE-8719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-8719: Assignee: Peter Ivanov (was: Kirill Tkalenko) > Index left partially built if a node crashes during index create or rebuild > --- > > Key: IGNITE-8719 > URL: https://issues.apache.org/jira/browse/IGNITE-8719 > Project: Ignite > Issue Type: Bug >Reporter: Alexey Goncharuk >Assignee: Peter Ivanov >Priority: Critical > Attachments: IndexRebuildAfterNodeCrashTest.java, > IndexRebuildingTest.java > > > Currently, we do not have any state associated with the index tree. Consider > the following scenario: > 1) Start node, put some data > 2) start CREATE INDEX operation > 3) Wait for a checkpoint and stop node before index create finished > 4) Restart node > Since the checkpoint finished, the new index tree will be persisted to the > disk, but not all data will be present in the index. > We should somehow store information about initializing index tree and mark it > valid only after all data is indexed. The state should be persisted as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14315) Ignite 3: Use maven-flatten plugin for project pom.xml
[ https://issues.apache.org/jira/browse/IGNITE-14315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17301560#comment-17301560 ] Peter Ivanov commented on IGNITE-14315: --- Everything looks good! > Ignite 3: Use maven-flatten plugin for project pom.xml > -- > > Key: IGNITE-14315 > URL: https://issues.apache.org/jira/browse/IGNITE-14315 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Goncharuk >Assignee: Alexey Goncharuk >Priority: Major > Fix For: 3.0.0-alpha2 > > Time Spent: 10m > Remaining Estimate: 0h > > Without the flatten it would be impossible to use the maven-published > artifacts of Ignite 3. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14298) DEVNOTES should contain clear instructions on how to run check-style
[
https://issues.apache.org/jira/browse/IGNITE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14298:
--
Summary: DEVNOTES should contain clear instructions on how to run
check-style (was: DEVNOTES should contain clear instructions on how to run
check-style.)
> DEVNOTES should contain clear instructions on how to run check-style
>
>
> Key: IGNITE-14298
> URL: https://issues.apache.org/jira/browse/IGNITE-14298
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Peter Ivanov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
>
> DEVNOTES should provide clear instructions on how to run the {{checkstyle}}
> && {{apache-rat}} targets for the project/particular sub-module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-14298) DEVNOTES should contain clear instructions on how to run check-style.
[
https://issues.apache.org/jira/browse/IGNITE-14298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-14298:
-
Assignee: Peter Ivanov
> DEVNOTES should contain clear instructions on how to run check-style.
> -
>
> Key: IGNITE-14298
> URL: https://issues.apache.org/jira/browse/IGNITE-14298
> Project: Ignite
> Issue Type: Bug
>Reporter: Vyacheslav Koptilin
>Assignee: Peter Ivanov
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-alpha2
>
>
> DEVNOTES should provide clear instructions on how to run the {{checkstyle}}
> && {{apache-rat}} targets for the project/particular sub-module.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov closed IGNITE-14151. - > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Attachments: Screenshot 2021-03-04 at 13.03.25.png > > Time Spent: 35m > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17295138#comment-17295138 ] Peter Ivanov commented on IGNITE-14151: --- I've tested integration (see screenshot): * Run All is triggered by new/updated pull request * TeamCity publishes checks result into PR [~vkulichenko] – do we need integration for all tests or only for sanity ones? > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Attachments: Screenshot 2021-03-04 at 13.03.25.png > > Time Spent: 25m > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov resolved IGNITE-14151. --- Resolution: Done > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Attachments: Screenshot 2021-03-04 at 13.03.25.png > > Time Spent: 25m > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14151: -- Attachment: Screenshot 2021-03-04 at 13.03.25.png > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Attachments: Screenshot 2021-03-04 at 13.03.25.png > > Time Spent: 25m > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14243) .NET: Upgrade ConfigurationManager dependency
[
https://issues.apache.org/jira/browse/IGNITE-14243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reassigned IGNITE-14243:
-
Assignee: Pavel Tupitsyn (was: Peter Ivanov)
> .NET: Upgrade ConfigurationManager dependency
> -
>
> Key: IGNITE-14243
> URL: https://issues.apache.org/jira/browse/IGNITE-14243
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ConfigurationManager dependency is limited to versions below 5 (see nuspec
> file) which causes problems when other dependencies want 5.0+.
> Test that Ignite is compatible with newer versions and extend the range of
> allowed versions
> {code:java}
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Reopened] (IGNITE-14243) .NET: Upgrade ConfigurationManager dependency
[
https://issues.apache.org/jira/browse/IGNITE-14243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov reopened IGNITE-14243:
---
Assignee: Peter Ivanov (was: Pavel Tupitsyn)
> .NET: Upgrade ConfigurationManager dependency
> -
>
> Key: IGNITE-14243
> URL: https://issues.apache.org/jira/browse/IGNITE-14243
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Peter Ivanov
>Priority: Major
> Labels: .NET
> Fix For: 2.11
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ConfigurationManager dependency is limited to versions below 5 (see nuspec
> file) which causes problems when other dependencies want 5.0+.
> Test that Ignite is compatible with newer versions and extend the range of
> allowed versions
> {code:java}
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14215) Website: Enable Lucky Orange and Yandex Metrics
[ https://issues.apache.org/jira/browse/IGNITE-14215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17292890#comment-17292890 ] Peter Ivanov commented on IGNITE-14215: --- No, I cannot. Possibly, [~agoncharuk] know where these metrics should be added? > Website: Enable Lucky Orange and Yandex Metrics > --- > > Key: IGNITE-14215 > URL: https://issues.apache.org/jira/browse/IGNITE-14215 > Project: Ignite > Issue Type: Bug > Components: website >Reporter: Denis A. Magda >Assignee: Mauricio Stekl >Priority: Major > > We're conducting a usability audit of the Ignite website to better understand > what parts of the site get more attention and what doesn't resonate with > developers landing on the pages. The goal is to introduce and explain Ignite > in the most concise and technical way, and to guide the users from the > landing pages to documentation and other pages so that they can transition > with their Ignite journey seamlessly. > > To better understand how the users perceive the information on the current > web pages, we need to see heatmaps and other advanced metrics that are > supported by the following tools: > * [https://www.luckyorange.com|https://www.luckyorange.com/] > * [https://metrica.yandex.com/about]? > Let's use the tools for the time of the audit. All the data is capture and > kept anonymous. > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-13999) Switch to SHA-512 for jar checksum calculation.
[ https://issues.apache.org/jira/browse/IGNITE-13999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov reassigned IGNITE-13999: - Assignee: (was: Peter Ivanov) > Switch to SHA-512 for jar checksum calculation. > --- > > Key: IGNITE-13999 > URL: https://issues.apache.org/jira/browse/IGNITE-13999 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Andrey Mashenkov >Priority: Major > Labels: ignite-3 > > maven-deploy-plugin is responsible for signing jar. However, it seems SHA-1 > is hardcoded there. > In the latest apache parent pom (org.apache:apache:23) a > checksum-maven-plugin is used as a workaround to sign jars with SHA-512. But > it signs only source jar and do not affect binary jar. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290669#comment-17290669 ] Peter Ivanov commented on IGNITE-14151: --- No restrictions as soon as account with token has access to target repository for push. > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > Time Spent: 0.25h > Remaining Estimate: 0h > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14151) Set up commit status publisher on TC
[ https://issues.apache.org/jira/browse/IGNITE-14151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290050#comment-17290050 ] Peter Ivanov commented on IGNITE-14151: --- [~vkulichenko], according to setup instructions, we need token with *_public_repo_* or *_repo_* scope. After that, I will be able to setup publishing integration. However, please, be advised, that this publishing is one way only and PR will receive any status only after build is completed (pending build is not shown AFAIK). > Set up commit status publisher on TC > > > Key: IGNITE-14151 > URL: https://issues.apache.org/jira/browse/IGNITE-14151 > Project: Ignite > Issue Type: Task >Reporter: Valentin Kulichenko >Assignee: Peter Ivanov >Priority: Major > Labels: teamcity > > 'Run All' build should publish the status to the appropriate PR on GitHub. We > will then update the process to allow merges only with successful builds. > See here: https://www.jetbrains.com/help/teamcity/commit-status-publisher.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14016) Prepare an RPM package for Ignite 3.0
[ https://issues.apache.org/jira/browse/IGNITE-14016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14016: -- Attachment: apache-ignite-3.0.0-1.noarch.rpm > Prepare an RPM package for Ignite 3.0 > - > > Key: IGNITE-14016 > URL: https://issues.apache.org/jira/browse/IGNITE-14016 > Project: Ignite > Issue Type: Task >Reporter: Peter Ivanov >Assignee: Peter Ivanov >Priority: Major > Attachments: apache-ignite-3.0.0-1.noarch.rpm, rhel.log > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14132) Add configuration to separate Integration and Unit tests
[
https://issues.apache.org/jira/browse/IGNITE-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17280847#comment-17280847
]
Peter Ivanov commented on IGNITE-14132:
---
Prepared
[https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_IntegrationTests?mode=builds]
> Add configuration to separate Integration and Unit tests
>
>
> Key: IGNITE-14132
> URL: https://issues.apache.org/jira/browse/IGNITE-14132
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After IGNITE-14123, Unit and Integration tests are separated.
> However, Maven goal {{integration-test}} includes unit tests too.
> There is an option to add external property to skip unit tests only which
> should be added to {{parent/pom.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14132) Add configuration to separate Integration and Unit tests
[
https://issues.apache.org/jira/browse/IGNITE-14132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ivanov updated IGNITE-14132:
--
Fix Version/s: 3.0.0-alpha2
> Add configuration to separate Integration and Unit tests
>
>
> Key: IGNITE-14132
> URL: https://issues.apache.org/jira/browse/IGNITE-14132
> Project: Ignite
> Issue Type: Bug
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 3.0.0-alpha2
>
>
> After IGNITE-14123, Unit and Integration tests are separated.
> However, Maven goal {{integration-test}} includes unit tests too.
> There is an option to add external property to skip unit tests only which
> should be added to {{parent/pom.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-14132) Add configuration to separate Integration and Unit tests
Peter Ivanov created IGNITE-14132:
-
Summary: Add configuration to separate Integration and Unit tests
Key: IGNITE-14132
URL: https://issues.apache.org/jira/browse/IGNITE-14132
Project: Ignite
Issue Type: Bug
Reporter: Peter Ivanov
Assignee: Peter Ivanov
After IGNITE-14123, Unit and Integration tests are separated.
However, Maven goal {{integration-test}} includes unit tests too.
There is an option to add external property to skip unit tests only which
should be added to {{parent/pom.xml}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14123) Separate unit tests from integration tests
[ https://issues.apache.org/jira/browse/IGNITE-14123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14123: -- Fix Version/s: 3.0.0-alpha2 > Separate unit tests from integration tests > -- > > Key: IGNITE-14123 > URL: https://issues.apache.org/jira/browse/IGNITE-14123 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Semyon Danilov >Assignee: Semyon Danilov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-13991) Add checkstyle test suite for pom files on TC.
[ https://issues.apache.org/jira/browse/IGNITE-13991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-13991: -- Fix Version/s: 3.0.0-alpha2 > Add checkstyle test suite for pom files on TC. > -- > > Key: IGNITE-13991 > URL: https://issues.apache.org/jira/browse/IGNITE-13991 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Andrey Mashenkov >Assignee: Peter Ivanov >Priority: Major > Labels: ignite-3 > Fix For: 3.0.0-alpha2 > > Time Spent: 20m > Remaining Estimate: 0h > > Create separate test suite for TC that should check that there are violations > of dependencyManagement/pluginManagement approach. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14124) Fix project's Maven settings
Peter Ivanov created IGNITE-14124: - Summary: Fix project's Maven settings Key: IGNITE-14124 URL: https://issues.apache.org/jira/browse/IGNITE-14124 Project: Ignite Issue Type: Bug Affects Versions: 3.0.0-alpha2 Reporter: Peter Ivanov Assignee: Peter Ivanov Fix For: 3.0.0-alpha2 https://ci.ignite.apache.org/buildConfiguration/ignite3_Tests_RunSanityCheck/5855660?buildTab=dependencies=list -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14017) Willing to add s390x support to the docker image.
[ https://issues.apache.org/jira/browse/IGNITE-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Ivanov updated IGNITE-14017: -- Fix Version/s: 2.11 > Willing to add s390x support to the docker image. > - > > Key: IGNITE-14017 > URL: https://issues.apache.org/jira/browse/IGNITE-14017 > Project: Ignite > Issue Type: New Feature >Reporter: Prajakta Chaudhari >Assignee: Ilya Murchenko >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > We are willing to add s390x support to the docker image. Dockerfile provided > on Apache Ignite GitHub repository > (https://github.com/apache/ignite/tree/master/docker/apache-ignite) is > working fine on s390x architecture. However we could not get any information > about how does the docker image build and release process work. Can you > please give some pointers to go ahead with the task? -- This message was sent by Atlassian Jira (v8.3.4#803005)
