[jira] [Assigned] (IGNITE-18582) Bootstrap Configuration: REST should modify conf file
[ https://issues.apache.org/jira/browse/IGNITE-18582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18582: -- Assignee: Mikhail Pochatkin > Bootstrap Configuration: REST should modify conf file > - > > Key: IGNITE-18582 > URL: https://issues.apache.org/jira/browse/IGNITE-18582 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18581) Bootstrap Configuration: don't save bootstrap configuration
[ https://issues.apache.org/jira/browse/IGNITE-18581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18581: -- Assignee: Mikhail Pochatkin > Bootstrap Configuration: don't save bootstrap configuration > > > Key: IGNITE-18581 > URL: https://issues.apache.org/jira/browse/IGNITE-18581 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18729) Ignite deployment manager
[ https://issues.apache.org/jira/browse/IGNITE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18729: --- Description: 1. Accept deployment unit. 2. Store unit on CMG. 3. Store unit metainformation (Sys table, metastorage?). 4. Undeploy unit. 5. Return list of deployed unit. > Ignite deployment manager > - > > Key: IGNITE-18729 > URL: https://issues.apache.org/jira/browse/IGNITE-18729 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > 1. Accept deployment unit. > 2. Store unit on CMG. > 3. Store unit metainformation (Sys table, metastorage?). > 4. Undeploy unit. > 5. Return list of deployed unit. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18729) Ignite deployment manager
[ https://issues.apache.org/jira/browse/IGNITE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18729: --- Description: (was: Basic implementation of deployment manager should cover next functionallity: 1. Stor) > Ignite deployment manager > - > > Key: IGNITE-18729 > URL: https://issues.apache.org/jira/browse/IGNITE-18729 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18729) Ignite deployment manager
[ https://issues.apache.org/jira/browse/IGNITE-18729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18729: --- Description: Basic implementation of deployment manager should cover next functionallity: 1. Stor > Ignite deployment manager > - > > Key: IGNITE-18729 > URL: https://issues.apache.org/jira/browse/IGNITE-18729 > Project: Ignite > Issue Type: New Feature >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Basic implementation of deployment manager should cover next functionallity: > 1. Stor -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18730) Rest API for deployment units
Mikhail Pochatkin created IGNITE-18730: -- Summary: Rest API for deployment units Key: IGNITE-18730 URL: https://issues.apache.org/jira/browse/IGNITE-18730 Project: Ignite Issue Type: New Feature Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18731) CLI command for deployment units
Mikhail Pochatkin created IGNITE-18731: -- Summary: CLI command for deployment units Key: IGNITE-18731 URL: https://issues.apache.org/jira/browse/IGNITE-18731 Project: Ignite Issue Type: New Feature Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18729) Ignite deployment manager
Mikhail Pochatkin created IGNITE-18729: -- Summary: Ignite deployment manager Key: IGNITE-18729 URL: https://issues.apache.org/jira/browse/IGNITE-18729 Project: Ignite Issue Type: New Feature Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18728) Code deployment for Ignite 3
Mikhail Pochatkin created IGNITE-18728: -- Summary: Code deployment for Ignite 3 Key: IGNITE-18728 URL: https://issues.apache.org/jira/browse/IGNITE-18728 Project: Ignite Issue Type: Epic Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18723) ClientArchTest should check client dependencies
Mikhail Pochatkin created IGNITE-18723: -- Summary: ClientArchTest should check client dependencies Key: IGNITE-18723 URL: https://issues.apache.org/jira/browse/IGNITE-18723 Project: Ignite Issue Type: Bug Reporter: Mikhail Pochatkin ClientArchTest should check not only client source code but also all depended Ignite modules. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18680) Fix ClientArchTest source provider
Mikhail Pochatkin created IGNITE-18680: -- Summary: Fix ClientArchTest source provider Key: IGNITE-18680 URL: https://issues.apache.org/jira/browse/IGNITE-18680 Project: Ignite Issue Type: Bug Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin org.apache.ignite.client.ClientArchTest take sources for analize from ignite-client.jar file from build/lib directory. This jar contains class files only from client module. However, in a normal build pipeline, the tests are run before the jar files are built and Gradle test task doesn't depend on jar task. As result, we have false failed test. So, us solution we can change location provider org.apache.ignite.client.ClientArchTest.ClassesWithLibsLocationProvider and took *.java files for analizing insted of class files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18582) Bootstrap Configuration: REST should modify conf file
Mikhail Pochatkin created IGNITE-18582: -- Summary: Bootstrap Configuration: REST should modify conf file Key: IGNITE-18582 URL: https://issues.apache.org/jira/browse/IGNITE-18582 Project: Ignite Issue Type: New Feature Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18581) Bootstrap Configuration: don't save bootstrap configuration
Mikhail Pochatkin created IGNITE-18581: -- Summary: Bootstrap Configuration: don't save bootstrap configuration Key: IGNITE-18581 URL: https://issues.apache.org/jira/browse/IGNITE-18581 Project: Ignite Issue Type: New Feature Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18553) When tests are run using IDEA runner, wrong lock format is used
[
https://issues.apache.org/jira/browse/IGNITE-18553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18553:
---
Component/s: build
> When tests are run using IDEA runner, wrong lock format is used
> ---
>
> Key: IGNITE-18553
> URL: https://issues.apache.org/jira/browse/IGNITE-18553
> Project: Ignite
> Issue Type: Bug
> Components: build
>Reporter: Roman Puchkovskiy
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> An example of such test is {{{}ItComputeTest{}}}. When run with Gradle
> Runner, I get the following in the log:
> 2023-01-16 11:41:06:381 +0400 [INFO][Test worker][ConnectionManager] Server
> started [address=/0:0:0:0:0:0:0:0:3344]
> But when I run same test with IDEA runner, I get this:
> янв. 16, 2023 12:01:03 PM org.apache.ignite.internal.logger.IgniteLogger
> logInternal
> INFO: Server started [address=/0:0:0:0:0:0:0:0:3344]
> The latter is wrong, so it looks like under IDEA runner our logging
> properties are not picked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18543) Remove missed pom.xml
Mikhail Pochatkin created IGNITE-18543: -- Summary: Remove missed pom.xml Key: IGNITE-18543 URL: https://issues.apache.org/jira/browse/IGNITE-18543 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin Remove missed pom.xml from distribution-zones module -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17692) Flaky test after introduce gradle build
[ https://issues.apache.org/jira/browse/IGNITE-17692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-17692. Resolution: Won't Fix > Flaky test after introduce gradle build > --- > > Key: IGNITE-17692 > URL: https://issues.apache.org/jira/browse/IGNITE-17692 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17487) Remove Maven build scripts
[ https://issues.apache.org/jira/browse/IGNITE-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17487: -- Assignee: Mikhail Pochatkin > Remove Maven build scripts > -- > > Key: IGNITE-17487 > URL: https://issues.apache.org/jira/browse/IGNITE-17487 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > 1. Remove Maven project from Apache Ignite 3 repo. > 2. Remove Maven project from CI. > 3. Start use Gradle project verification as default for PR visa. > 4. Change WorkDirectoryExtension to write log files for tests to the build > directory. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18222) Implement the rest of dynamic completors
[ https://issues.apache.org/jira/browse/IGNITE-18222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17653101#comment-17653101 ] Mikhail Pochatkin commented on IGNITE-18222: LGTM > Implement the rest of dynamic completors > > > Key: IGNITE-18222 > URL: https://issues.apache.org/jira/browse/IGNITE-18222 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Ivan Gagarkin >Priority: Major > Labels: ignite-3 > Time Spent: 2h 10m > Remaining Estimate: 0h > > There is a micro-framework to implement completers for commands and options > called Dynamic Completions. Now there are only two completers implemented: > hocon config completer and node name completer. But there are more options > and commands that could be auto-suggested. > Here is the list of them, that could be extended: > - script-file > - cluster-url > - jdbc-url > - help (include in sql mode) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18220) Integration tests for interactive suggestions
[ https://issues.apache.org/jira/browse/IGNITE-18220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652196#comment-17652196 ] Mikhail Pochatkin commented on IGNITE-18220: LGTM > Integration tests for interactive suggestions > - > > Key: IGNITE-18220 > URL: https://issues.apache.org/jira/browse/IGNITE-18220 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3 > Time Spent: 50m > Remaining Estimate: 0h > > CLI has it's own mechanism of completions in interactive mode – Dynamic > completions. This mechanism is tested only with unit tests which are not > enough. > Dynamic completers are used together with picocli completers and this > integration might provide an unexpected list of suggestions. > I propose to implement integration tests with real Ignite 3 cluster and with > picocli completions. The class to test is IgnitePicocliCommands. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18253) Jacoco integration test report
[ https://issues.apache.org/jira/browse/IGNITE-18253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17652158#comment-17652158 ] Mikhail Pochatkin commented on IGNITE-18253: https://github.com/apache/ignite-3/pull/1420 > Jacoco integration test report > -- > > Key: IGNITE-18253 > URL: https://issues.apache.org/jira/browse/IGNITE-18253 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Currently, jacoco report contains only unit test coverage. Need to include > integration tests also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18296) Review dependency hell and specify versions in classpath
[ https://issues.apache.org/jira/browse/IGNITE-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18296: -- Assignee: Mikhail Pochatkin > Review dependency hell and specify versions in classpath > > > Key: IGNITE-18296 > URL: https://issues.apache.org/jira/browse/IGNITE-18296 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: Test Results - ItComputeTest.html, screenshot-1.png > > Time Spent: 10m > Remaining Estimate: 0h > > Currently, several dependencies has more than one versions in classpath (see > attachments). Need to filter and specify strict version of dependency which > should be used in classpath -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18230) Packaging: MSI installer for winget package
[ https://issues.apache.org/jira/browse/IGNITE-18230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17650800#comment-17650800 ] Mikhail Pochatkin commented on IGNITE-18230: LGTM > Packaging: MSI installer for winget package > --- > > Key: IGNITE-18230 > URL: https://issues.apache.org/jira/browse/IGNITE-18230 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Creating winget package requires an installer so we need to create one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18280) Declare proper dependencies in the packaging tasks
[
https://issues.apache.org/jira/browse/IGNITE-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17649599#comment-17649599
]
Mikhail Pochatkin commented on IGNITE-18280:
LGTM
> Declare proper dependencies in the packaging tasks
> --
>
> Key: IGNITE-18280
> URL: https://issues.apache.org/jira/browse/IGNITE-18280
> Project: Ignite
> Issue Type: Improvement
> Components: build
>Reporter: Vadim Pakhnushev
>Assignee: Vadim Pakhnushev
>Priority: Major
> Labels: ignite-3
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When running `prepareRelease` task, gradle complains about tasks using output
> of other tasks without declaring a dependency.
> {code:java}
> > Task :packaging:signAllDistZip
> Execution optimizations have been disabled for task
> ':packaging:signAllDistZip' to ensure correctness due to the following
> reasons:
> - Gradle detected a problem with the following location:
> 'C:\ignite-3\packaging\build\distributions\ignite3-3.0.0-SNAPSHOT.zip'.
> Reason: Task ':packaging:signAllDistZip' uses this output of task
> ':packaging:createChecksums' without declaring an explicit or implicit
> dependency. This can lead to incorrect results being produced, depending on
> what order the tasks are executed. Please refer to
> https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency
> for more details about this problem.
> > Task :packaging:signAllSrcZip
> Execution optimizations have been disabled for task
> ':packaging:signAllSrcZip' to ensure correctness due to the following reasons:
> - Gradle detected a problem with the following location:
> 'C:\ignite-3\packaging\build\distributions\apache-ignite-3.0.0-SNAPSHOT-src.zip'.
> Reason: Task ':packaging:signAllSrcZip' uses this output of task
> ':packaging:createChecksums' without declaring an explicit or implicit
> dependency...
> > Task :packaging-cli:replacePostInstallScriptVars
> Execution optimizations have been disabled for task
> ':packaging-cli:replacePostInstallScriptVars' to ensure correctness due to
> the following reasons:
> - Gradle detected a problem with the following location:
> 'C:\ignite-3\packaging\cli\build'. Reason: Task ':packaging-cli:distZip' uses
> this output of task ':packaging-cli:replacePostInstallScriptVars' without
> declaring an explicit or implicit dependency...
> ...
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18391) Bootstrap configuration UX improvement
Mikhail Pochatkin created IGNITE-18391: -- Summary: Bootstrap configuration UX improvement Key: IGNITE-18391 URL: https://issues.apache.org/jira/browse/IGNITE-18391 Project: Ignite Issue Type: Epic Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18360) Migrate storage to new Binary Tuple format
[ https://issues.apache.org/jira/browse/IGNITE-18360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18360: --- Component/s: jdbc > Migrate storage to new Binary Tuple format > -- > > Key: IGNITE-18360 > URL: https://issues.apache.org/jira/browse/IGNITE-18360 > Project: Ignite > Issue Type: Improvement > Components: jdbc >Reporter: Konstantin Orlov >Priority: Major > Labels: ignite-3 > > The Binary Tuple Format was introduced in > [IEP-92|https://cwiki.apache.org/confluence/display/IGNITE/IEP-92%3A+Binary+Tuple+Format] > as replacement of > [IEP-54|https://cwiki.apache.org/confluence/display/IGNITE/IEP-54%3A+Schema-first+Approach] > Binary Row. However, the Ignite's core is still operating rows in BinaryRow > format. Let's start the migration to the new format. > Under current ticket it's proposed to migrate the storage only, as these > changes looks predictable and isolated, whereas it allows to start migration > in SQL engine as well. > The migration plan is as follow: > # Introduce new entity named TableRow. > Unlike the indexes, the table may evolve over time, thus schema of the binary > tuple may change as well. To make the storage a schema agnostic, it's > proposed to store only the version of the schema and a ByteBuffer > representing the data in the Binary Tuple format. > # Migrate all table-related storage interfaces and PartitionListener to the > new format > # Make conversion in the PartitionReplicaListener from BinaryRow to TableRow > and vice versa on the edge Replica-Storage integration (in the context of > this issue I consider the PartitionListener as part of the storage). > PartitionReplicaListener (PRL) seems to be a good choice to make such a > conversion because of 1) current implementation of row comparison for > deleteExact operation can't properly handle the schema changes, and thus the > notion of the schema has to be brought to this level, and 2) PRL is build > upon async calls, so it will be easy to incorporate awaiting of schema in > case the node stales a bit. > NB: during conversion, I would prefer to restore the logical order of the > columns and build the tuple in that order, rather than keep the physical > order of BinaryRow -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-17920) Develop docker-compose file for Ignite cluster
[ https://issues.apache.org/jira/browse/IGNITE-17920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644752#comment-17644752 ] Mikhail Pochatkin commented on IGNITE-17920: LGTM > Develop docker-compose file for Ignite cluster > -- > > Key: IGNITE-17920 > URL: https://issues.apache.org/jira/browse/IGNITE-17920 > Project: Ignite > Issue Type: Task > Components: build >Reporter: Aleksandr >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > The simplest pattern for docker distribution is working: > - pull docker image > - run docker container > - connect to the node from the developer machine > But there is another case of usage: > - get the compose file that forms the cluster (3 nodes) > - adjust the compose file if needed: change the cluster name, number of > nodes, etc > - docker compose up > - connect to the formed cluster from the developer machine > The second case is more likely to be used by devs, we have to develop the > compose file that will be mentioned in examples/docs. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18092) Fix zip distribution name providing to sign and checksum tasks
[ https://issues.apache.org/jira/browse/IGNITE-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644753#comment-17644753 ] Mikhail Pochatkin commented on IGNITE-18092: LGTM > Fix zip distribution name providing to sign and checksum tasks > -- > > Key: IGNITE-18092 > URL: https://issues.apache.org/jira/browse/IGNITE-18092 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Currently, createChecksums tasks in the packaging module have hard-coded zip > path and name of artifact. Need to remove hard-coded name of zip distribution. > Also, all other packaging-related tasks should be checked for distribution > name usage. Probably, it is a good idea to separate distribution name to some > global value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18340) Gradle build doesn't produce OpenAPI spec
[ https://issues.apache.org/jira/browse/IGNITE-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644722#comment-17644722 ] Mikhail Pochatkin commented on IGNITE-18340: LGTM > Gradle build doesn't produce OpenAPI spec > - > > Key: IGNITE-18340 > URL: https://issues.apache.org/jira/browse/IGNITE-18340 > Project: Ignite > Issue Type: Bug > Components: rest >Reporter: Vadim Pakhnushev >Assignee: Vadim Pakhnushev >Priority: Major > Labels: ignite-3 > Time Spent: 20m > Remaining Estimate: 0h > > Building :ignite-rest:classes should produce openapi/openapi.yaml file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Mikhail Pochatkin reassigned IGNITE-13999: -- Assignee: Mikhail Pochatkin > 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 >Assignee: Mikhail Pochatkin >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.20.10#820010)
[jira] [Resolved] (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 ] Mikhail Pochatkin resolved IGNITE-13999. Resolution: Won't Fix Done in IGNITE-18040 > 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 >Assignee: Mikhail Pochatkin >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.20.10#820010)
[jira] [Resolved] (IGNITE-15452) [Ignite 3] Add JavaDoc style check to the build lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-15452. Resolution: Won't Fix Done in IGNITE-17483 > [Ignite 3] Add JavaDoc style check to the build lifecycle > - > > Key: IGNITE-15452 > URL: https://issues.apache.org/jira/browse/IGNITE-15452 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Similar to IGNITE-15370, we need to enable the JavaDoc style checks as a part > of the build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-15451) [Ignite 3] Add PMD check to the build lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-15451. Resolution: Won't Fix Done in IGNITE-17483 > [Ignite 3] Add PMD check to the build lifecycle > --- > > Key: IGNITE-15451 > URL: https://issues.apache.org/jira/browse/IGNITE-15451 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Similar to IGNITE-15370, we need to enable the PMD checks as a part of the > build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18183) Rest endpoint for all node metrics
[
https://issues.apache.org/jira/browse/IGNITE-18183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18183:
---
Component/s: rest
> Rest endpoint for all node metrics
> --
>
> Key: IGNITE-18183
> URL: https://issues.apache.org/jira/browse/IGNITE-18183
> Project: Ignite
> Issue Type: Task
> Components: ignite-3, rest
>Reporter: Stepachev Maksim
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> *The problem:*
> The ignite 3 rest of clusters will usually be hided behind a load balancer,
> as result we aren't able to get a particular node metrics. In this task is
> required to develop an endpoint at your discretion that will extract metrics
> from all nodes by one call.
> *Possible path at your wish:*
> * /all-nodes/metrics
> * {{/node/all/metrics}} - query all nodes (like {{all-nodes}} above)
> * {{/node/12345678-1234-1234-1234-12345678/metrics}} - query that particular
> node even if we happen to connect to a different one{{{}{}}}
> * {{/node/local/metrics}} - query the node we connected to
> *Please look at these examples of other databases:*
> *
> [https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-nodes-stats.html]
> *
> [https://docs.spring.io/spring-boot/docs/current/actuator-api/htmlsingle/#metrics]
> * [https://micronaut-projects.github.io/micronaut-micrometer/latest/guide/]
> * Etc.
> It would be good if we could add filters to get specific sets of metrics.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IGNITE-18298) Enable assertions in Ignite nodes run from Dotnet tests
[
https://issues.apache.org/jira/browse/IGNITE-18298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17641713#comment-17641713
]
Mikhail Pochatkin commented on IGNITE-18298:
LGTM
> Enable assertions in Ignite nodes run from Dotnet tests
> ---
>
> Key: IGNITE-18298
> URL: https://issues.apache.org/jira/browse/IGNITE-18298
> Project: Ignite
> Issue Type: Improvement
>Reporter: Roman Puchkovskiy
>Assignee: Roman Puchkovskiy
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently, Ignite nodes are run without {{-ea}} flag which should be used in
> test environments.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18296) Review dependency hell and specify versions in classpath
[ https://issues.apache.org/jira/browse/IGNITE-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18296: --- Description: Currently, several dependencies has more than one versions in classpath (see attachments). Need to filter and specify strict version of dependency which should be used in classpath > Review dependency hell and specify versions in classpath > > > Key: IGNITE-18296 > URL: https://issues.apache.org/jira/browse/IGNITE-18296 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: screenshot-1.png > > > Currently, several dependencies has more than one versions in classpath (see > attachments). Need to filter and specify strict version of dependency which > should be used in classpath -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18296) Review dependency hell and specify versions in classpath
[ https://issues.apache.org/jira/browse/IGNITE-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18296: --- Attachment: screenshot-1.png > Review dependency hell and specify versions in classpath > > > Key: IGNITE-18296 > URL: https://issues.apache.org/jira/browse/IGNITE-18296 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Attachments: screenshot-1.png > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18296) Review dependency hell and specify versions in classpath
Mikhail Pochatkin created IGNITE-18296: -- Summary: Review dependency hell and specify versions in classpath Key: IGNITE-18296 URL: https://issues.apache.org/jira/browse/IGNITE-18296 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin Attachments: screenshot-1.png -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18289) Try native-image compilation for Ignite CLI
Mikhail Pochatkin created IGNITE-18289: -- Summary: Try native-image compilation for Ignite CLI Key: IGNITE-18289 URL: https://issues.apache.org/jira/browse/IGNITE-18289 Project: Ignite Issue Type: Improvement Components: cli Reporter: Mikhail Pochatkin * Check GraalVM native-image compilation for Ignite CLI * Provide metrics of start time, command execution, compilation time -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18253) Jacoco integration test report
[ https://issues.apache.org/jira/browse/IGNITE-18253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18253: -- Assignee: Mikhail Pochatkin > Jacoco integration test report > -- > > Key: IGNITE-18253 > URL: https://issues.apache.org/jira/browse/IGNITE-18253 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Currently, jacoco report contains only unit test coverage. Need to include > integration tests also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18250) Mark integrationTest folder as test sourse set
[ https://issues.apache.org/jira/browse/IGNITE-18250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18250: -- Assignee: Mikhail Pochatkin > Mark integrationTest folder as test sourse set > -- > > Key: IGNITE-18250 > URL: https://issues.apache.org/jira/browse/IGNITE-18250 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Currently, in IDEA integration test sourse set marked as regular source set, > not test source set. Need to add integrationTest folder to test source set > collection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18270) Fix checkstyle in ignite-runner module
[ https://issues.apache.org/jira/browse/IGNITE-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18270: --- Description: Currently, few modules have disable checkstyle check, need to enable it. > Fix checkstyle in ignite-runner module > -- > > Key: IGNITE-18270 > URL: https://issues.apache.org/jira/browse/IGNITE-18270 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, few modules have disable checkstyle check, need to enable it. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18270) Fix checkstyle in ignite-runner module
[ https://issues.apache.org/jira/browse/IGNITE-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18270: -- Assignee: Mikhail Pochatkin > Fix checkstyle in ignite-runner module > -- > > Key: IGNITE-18270 > URL: https://issues.apache.org/jira/browse/IGNITE-18270 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18270) Fix checkstyle in ignite-runner module
Mikhail Pochatkin created IGNITE-18270: -- Summary: Fix checkstyle in ignite-runner module Key: IGNITE-18270 URL: https://issues.apache.org/jira/browse/IGNITE-18270 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IGNITE-18263) Fix REST API version in the generated openapi.yaml
[
https://issues.apache.org/jira/browse/IGNITE-18263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17638646#comment-17638646
]
Mikhail Pochatkin commented on IGNITE-18263:
LGTM
> Fix REST API version in the generated openapi.yaml
> --
>
> Key: IGNITE-18263
> URL: https://issues.apache.org/jira/browse/IGNITE-18263
> Project: Ignite
> Issue Type: Bug
> Components: build
>Reporter: Mikhail Pochatkin
>Assignee: Roman Puchkovskiy
>Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {{openapi.yaml}} is generated during build. It must contain version
> 3.0.0-SNAPSHOT, but in reality version 3.0.0-alpha is generated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18263) Fix REST API version
Mikhail Pochatkin created IGNITE-18263: -- Summary: Fix REST API version Key: IGNITE-18263 URL: https://issues.apache.org/jira/browse/IGNITE-18263 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18253) Jacoco integration test report
Mikhail Pochatkin created IGNITE-18253: -- Summary: Jacoco integration test report Key: IGNITE-18253 URL: https://issues.apache.org/jira/browse/IGNITE-18253 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin Currently, jacoco report contains only unit test coverage. Need to include integration tests also. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18250) Mark integrationTest folder as test sourse set
Mikhail Pochatkin created IGNITE-18250: -- Summary: Mark integrationTest folder as test sourse set Key: IGNITE-18250 URL: https://issues.apache.org/jira/browse/IGNITE-18250 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin Currently, in IDEA integration test sourse set marked as regular source set, not test source set. Need to add integrationTest folder to test source set collection. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18092) Fix zip distribution name providing to sign and checksum tasks
[ https://issues.apache.org/jira/browse/IGNITE-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18092: -- Assignee: Vadim Pakhnushev > Fix zip distribution name providing to sign and checksum tasks > -- > > Key: IGNITE-18092 > URL: https://issues.apache.org/jira/browse/IGNITE-18092 > Project: Ignite > Issue Type: Improvement > Components: build, ignite-3 >Reporter: Mikhail Pochatkin >Assignee: Vadim Pakhnushev >Priority: Major > Labels: build, ignite-3 > > Currently, createChecksums tasks in the packaging module have hard-coded zip > path and name of artifact. Need to remove hard-coded name of zip distribution. > Also, all other packaging-related tasks should be checked for distribution > name usage. Probably, it is a good idea to separate distribution name to some > global value. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18152) Fix creds reading in repository deploy build
[ https://issues.apache.org/jira/browse/IGNITE-18152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18152: -- Assignee: Mikhail Pochatkin > Fix creds reading in repository deploy build > > > Key: IGNITE-18152 > URL: https://issues.apache.org/jira/browse/IGNITE-18152 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > > Currently, in buildscripts/publishing-repos.gradle script creds reading made > via gradle.properties and release manager should define username\password in > local gradle.properties file, but it doesn't work now, only with direct creds > definition in script is working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18185) .NET: Thin 3.0: Automate NuGet publish process
[
https://issues.apache.org/jira/browse/IGNITE-18185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18185:
---
Component/s: build
Labels: .NET buid ignite-3 (was: .NET ignite-3)
> .NET: Thin 3.0: Automate NuGet publish process
> --
>
> Key: IGNITE-18185
> URL: https://issues.apache.org/jira/browse/IGNITE-18185
> Project: Ignite
> Issue Type: Improvement
> Components: build, platforms
>Reporter: Pavel Tupitsyn
>Priority: Major
> Labels: .NET, buid, ignite-3
> Fix For: 3.0.0-beta2
>
>
> Described below is the process to push nupkg/snupkg packages to nuget.org.
> *Prerequisites*
> * .NET SDK 6 https://dotnet.microsoft.com/en-us/download/dotnet/6.0
> *Process*
> * For every file in *apache-ignite-VER-nuget.zip*:
> {code}
> dotnet nuget push $FILE --api-key $API_KEY --source "https://nuget.org/;
> {code}
> The API_KEY can be found at
> https://svn.apache.org/repos/private/pmc/ignite/credentials/nuget.org (PMC
> only, requires Apache credentials).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (IGNITE-15453) [Ignite 3] Research options for vulnerability scanning
[ https://issues.apache.org/jira/browse/IGNITE-15453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-15453: -- Assignee: Mikhail Pochatkin (was: Petr Ivanov) > [Ignite 3] Research options for vulnerability scanning > -- > > Key: IGNITE-15453 > URL: https://issues.apache.org/jira/browse/IGNITE-15453 > Project: Ignite > Issue Type: Task > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > We need some kind of vulnerability scanning for Ignite 3. Let's research the > options. > As one of the possible solutions: https://github.com/aquasecurity/trivy -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-15451) [Ignite 3] Add PMD check to the build lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-15451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-15451: -- Assignee: Mikhail Pochatkin (was: Petr Ivanov) > [Ignite 3] Add PMD check to the build lifecycle > --- > > Key: IGNITE-15451 > URL: https://issues.apache.org/jira/browse/IGNITE-15451 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Similar to IGNITE-15370, we need to enable the PMD checks as a part of the > build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-15452) [Ignite 3] Add JavaDoc style check to the build lifecycle
[ https://issues.apache.org/jira/browse/IGNITE-15452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-15452: -- Assignee: Mikhail Pochatkin (was: Petr Ivanov) > [Ignite 3] Add JavaDoc style check to the build lifecycle > - > > Key: IGNITE-15452 > URL: https://issues.apache.org/jira/browse/IGNITE-15452 > Project: Ignite > Issue Type: Improvement > Components: build >Affects Versions: 3.0.0-alpha2 >Reporter: Valentin Kulichenko >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Similar to IGNITE-15370, we need to enable the JavaDoc style checks as a part > of the build. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18151) Create folder if not exist in scr zip build task
[ https://issues.apache.org/jira/browse/IGNITE-18151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18151: --- Labels: ignite-3 (was: ) > Create folder if not exist in scr zip build task > > > Key: IGNITE-18151 > URL: https://issues.apache.org/jira/browse/IGNITE-18151 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > In IGNITE-18129 introduced task allSrcZip which creating zip snapshot with > current code base. This src zip needed for release. > 1. Need to add check before git archive command that build\distribution > folder is exist because git will fail in case when folder doesn't exist. > 2. Fix prefix path, need to add \ in end of prefix path -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18152) Fix creds reading in repository deploy build
Mikhail Pochatkin created IGNITE-18152: -- Summary: Fix creds reading in repository deploy build Key: IGNITE-18152 URL: https://issues.apache.org/jira/browse/IGNITE-18152 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin Currently, in buildscripts/publishing-repos.gradle script creds reading made via gradle.properties and release manager should define username\password in local gradle.properties file, but it doesn't work now, only with direct creds definition in script is working. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18151) Create folder if not exist in scr zip build task
Mikhail Pochatkin created IGNITE-18151: -- Summary: Create folder if not exist in scr zip build task Key: IGNITE-18151 URL: https://issues.apache.org/jira/browse/IGNITE-18151 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin In IGNITE-18129 introduced task allSrcZip which creating zip snapshot with current code base. This src zip needed for release. 1. Need to add check before git archive command that build\distribution folder is exist because git will fail in case when folder doesn't exist. 2. Fix prefix path, need to add \ in end of prefix path -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18129) Fix Ignite 3 build and publishing for beta 1
[ https://issues.apache.org/jira/browse/IGNITE-18129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18129: -- Assignee: Mikhail Pochatkin > Fix Ignite 3 build and publishing for beta 1 > > > Key: IGNITE-18129 > URL: https://issues.apache.org/jira/browse/IGNITE-18129 > Project: Ignite > Issue Type: Bug >Reporter: Stanislav Lukyanov >Assignee: Mikhail Pochatkin >Priority: Major > > Need to make a few small fixes in the build and publishing process: > * Fix the readme to mention beta 1 instead of alpha 5 > * Automatically build and sign src.zip > * Automatically build and sign .NET NuGet package (package .nuget into a > .nuget.zip like it is done in 2.x) > * Update release.md as needed > The following artifacts need to be uploaded to the release repository: > * src.zip > * ignite: zip, rpm, deb > * ignite-db: zip, rpm, deb > * ignite-client: jar > * nuget.zip -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18116) Fix RELEASE.md
[
https://issues.apache.org/jira/browse/IGNITE-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18116:
---
Description:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
{code:java}
git archive `--prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD`
{code}
Also need add automatization of signing of this source zip
was:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
{code:java}
git archive `--prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD`
{code}
> Fix RELEASE.md
> ---
>
> Key: IGNITE-18116
> URL: https://issues.apache.org/jira/browse/IGNITE-18116
> Project: Ignite
> Issue Type: Bug
> Components: ignite-3
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Currently, RELEASE.md file missed part of fat source zip building, need to
> add it.
> Made source zip via
> {code:java}
> git archive `--prefix=apache-ignite-{version}-src/ -o
> apache-ignite-{version}-src.zip HEAD`
> {code}
> Also need add automatization of signing of this source zip
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18092) Fix zip distribution name providing to sign and checksum tasks
[ https://issues.apache.org/jira/browse/IGNITE-18092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18092: --- Description: Currently, createChecksums tasks in packaging module have hard coded zip path and name of artifact. Need to remove hard coded name of zip distribution > Fix zip distribution name providing to sign and checksum tasks > -- > > Key: IGNITE-18092 > URL: https://issues.apache.org/jira/browse/IGNITE-18092 > Project: Ignite > Issue Type: Improvement > Components: build, ignite-3 >Reporter: Mikhail Pochatkin >Priority: Major > Labels: build, ignite-3 > > Currently, createChecksums tasks in packaging module have hard coded zip path > and name of artifact. Need to remove hard coded name of zip distribution -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18116) Fix RELEASE.md
[
https://issues.apache.org/jira/browse/IGNITE-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18116:
---
Labels: ignite-3 (was: )
> Fix RELEASE.md
> ---
>
> Key: IGNITE-18116
> URL: https://issues.apache.org/jira/browse/IGNITE-18116
> Project: Ignite
> Issue Type: Bug
> Components: ignite-3
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3
>
> Currently, RELEASE.md file missed part of fat source zip building, need to
> add it.
> Made source zip via
> {code:java}
> git archive `--prefix=apache-ignite-{version}-src/ -o
> apache-ignite-{version}-src.zip HEAD`
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18116) Fix RELEASE.md
[
https://issues.apache.org/jira/browse/IGNITE-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18116:
---
Description:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
{code:java}
git archive `--prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD`
{code}
was:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
git archive `--prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD`
> Fix RELEASE.md
> ---
>
> Key: IGNITE-18116
> URL: https://issues.apache.org/jira/browse/IGNITE-18116
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Pochatkin
>Priority: Major
>
> Currently, RELEASE.md file missed part of fat source zip building, need to
> add it.
> Made source zip via
> {code:java}
> git archive `--prefix=apache-ignite-{version}-src/ -o
> apache-ignite-{version}-src.zip HEAD`
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18116) Fix RELEASE.md
[
https://issues.apache.org/jira/browse/IGNITE-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18116:
---
Component/s: ignite-3
> Fix RELEASE.md
> ---
>
> Key: IGNITE-18116
> URL: https://issues.apache.org/jira/browse/IGNITE-18116
> Project: Ignite
> Issue Type: Bug
> Components: ignite-3
>Reporter: Mikhail Pochatkin
>Priority: Major
>
> Currently, RELEASE.md file missed part of fat source zip building, need to
> add it.
> Made source zip via
> {code:java}
> git archive `--prefix=apache-ignite-{version}-src/ -o
> apache-ignite-{version}-src.zip HEAD`
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (IGNITE-18116) Fix RELEASE.md
Mikhail Pochatkin created IGNITE-18116:
--
Summary: Fix RELEASE.md
Key: IGNITE-18116
URL: https://issues.apache.org/jira/browse/IGNITE-18116
Project: Ignite
Issue Type: Bug
Reporter: Mikhail Pochatkin
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
git archive --prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-18116) Fix RELEASE.md
[
https://issues.apache.org/jira/browse/IGNITE-18116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-18116:
---
Description:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
git archive `--prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD`
was:
Currently, RELEASE.md file missed part of fat source zip building, need to add
it.
Made source zip via
git archive --prefix=apache-ignite-{version}-src/ -o
apache-ignite-{version}-src.zip HEAD
> Fix RELEASE.md
> ---
>
> Key: IGNITE-18116
> URL: https://issues.apache.org/jira/browse/IGNITE-18116
> Project: Ignite
> Issue Type: Bug
>Reporter: Mikhail Pochatkin
>Priority: Major
>
> Currently, RELEASE.md file missed part of fat source zip building, need to
> add it.
> Made source zip via
> git archive `--prefix=apache-ignite-{version}-src/ -o
> apache-ignite-{version}-src.zip HEAD`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17487) Remove Maven build scripts
[ https://issues.apache.org/jira/browse/IGNITE-17487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17487: --- Description: 1. Remove Maven project from Apache Ignite 3 repo 2. Remove Maven project from CI 3. Start use Gradle project verification as default for PR visa > Remove Maven build scripts > -- > > Key: IGNITE-17487 > URL: https://issues.apache.org/jira/browse/IGNITE-17487 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > 1. Remove Maven project from Apache Ignite 3 repo > 2. Remove Maven project from CI > 3. Start use Gradle project verification as default for PR visa -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18110) Modernize gradle build cache
[ https://issues.apache.org/jira/browse/IGNITE-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18110: -- Assignee: Mikhail Pochatkin > Modernize gradle build cache > -- > > Key: IGNITE-18110 > URL: https://issues.apache.org/jira/browse/IGNITE-18110 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: build, ignite-3 > > 1. Use gradle build cache only in CI env. > 2. Disable build cache for Test tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18110) Modernize gradle build cache
[ https://issues.apache.org/jira/browse/IGNITE-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18110: --- Summary: Modernize gradle build cache(was: Modernize gradle cache build ) > Modernize gradle build cache > -- > > Key: IGNITE-18110 > URL: https://issues.apache.org/jira/browse/IGNITE-18110 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: build, ignite-3 > > 1. Use gradle build cache only in CI env. > 2. Disable build cache for Test tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18110) Modernize gradle cache build
[ https://issues.apache.org/jira/browse/IGNITE-18110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18110: --- Description: 1. Use gradle build cache only in CI env. 2. Disable build cache for Test tasks > Modernize gradle cache build > - > > Key: IGNITE-18110 > URL: https://issues.apache.org/jira/browse/IGNITE-18110 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: build, ignite-3 > > 1. Use gradle build cache only in CI env. > 2. Disable build cache for Test tasks -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18110) Modernize gradle cache build
Mikhail Pochatkin created IGNITE-18110: -- Summary: Modernize gradle cache build Key: IGNITE-18110 URL: https://issues.apache.org/jira/browse/IGNITE-18110 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18092) Fix zip distribution name providing to sign and checksum tasks
Mikhail Pochatkin created IGNITE-18092: -- Summary: Fix zip distribution name providing to sign and checksum tasks Key: IGNITE-18092 URL: https://issues.apache.org/jira/browse/IGNITE-18092 Project: Ignite Issue Type: Improvement Components: build, ignite-3 Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-18040) Add GPG sign plugin to Gradle
[ https://issues.apache.org/jira/browse/IGNITE-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-18040: --- Description: For release via Gradle we need to add signing mechanism which required by Apache Release politics. We need to sign all jars, zip distributions and DEB\RPM packages > Add GPG sign plugin to Gradle > - > > Key: IGNITE-18040 > URL: https://issues.apache.org/jira/browse/IGNITE-18040 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 10m > Remaining Estimate: 0h > > For release via Gradle we need to add signing mechanism which required by > Apache Release politics. > We need to sign all jars, zip distributions and DEB\RPM packages -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-18040) Add GPG sign plugin to Gradle
[ https://issues.apache.org/jira/browse/IGNITE-18040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-18040: -- Assignee: Mikhail Pochatkin > Add GPG sign plugin to Gradle > - > > Key: IGNITE-18040 > URL: https://issues.apache.org/jira/browse/IGNITE-18040 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18040) Add GPG sign plugin to Gradle
Mikhail Pochatkin created IGNITE-18040: -- Summary: Add GPG sign plugin to Gradle Key: IGNITE-18040 URL: https://issues.apache.org/jira/browse/IGNITE-18040 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-18009) Fix gradle build
Mikhail Pochatkin created IGNITE-18009: -- Summary: Fix gradle build Key: IGNITE-18009 URL: https://issues.apache.org/jira/browse/IGNITE-18009 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17965) Enable remote build cache for Gradle
[ https://issues.apache.org/jira/browse/IGNITE-17965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17965: -- Assignee: Mikhail Pochatkin > Enable remote build cache for Gradle > > > Key: IGNITE-17965 > URL: https://issues.apache.org/jira/browse/IGNITE-17965 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to enable remote build cache feature for Gradle on CI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17966) Fix problem with stuck Gradle processes in .NET tests
Mikhail Pochatkin created IGNITE-17966: -- Summary: Fix problem with stuck Gradle processes in .NET tests Key: IGNITE-17966 URL: https://issues.apache.org/jira/browse/IGNITE-17966 Project: Ignite Issue Type: Bug Components: build Reporter: Mikhail Pochatkin Currently, when .NET test suite finished some Gradle processes will alive and after that CI agents start be in inconsistance state. The main problem is using ports and next build will be failed because of unreachable port. So, need to fix this problem and kill all processes which producing in build time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17966) Fix problem with stuck Gradle processes in .NET tests
[ https://issues.apache.org/jira/browse/IGNITE-17966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17966: -- Assignee: Mikhail Pochatkin > Fix problem with stuck Gradle processes in .NET tests > - > > Key: IGNITE-17966 > URL: https://issues.apache.org/jira/browse/IGNITE-17966 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Blocker > Labels: ignite-3 > > Currently, when .NET test suite finished some Gradle processes will alive and > after that CI agents start be in inconsistance state. The main problem is > using ports and next build will be failed because of unreachable port. So, > need to fix this problem and kill all processes which producing in build > time. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (IGNITE-17714) Split integration test in ignite-runner module
[ https://issues.apache.org/jira/browse/IGNITE-17714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin resolved IGNITE-17714. Resolution: Fixed Fixed in IGNITE-17486 > Split integration test in ignite-runner module > -- > > Key: IGNITE-17714 > URL: https://issues.apache.org/jira/browse/IGNITE-17714 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > Time Spent: 0.5h > Remaining Estimate: 0h > > Ignite-runner module contains tests with "sqllogic" tag and need to create > separate gradle tasks for it. > Currently, maven build has two different configurations which provide > possibility to run different test suites with "sqllogic" tag and without > separatly. Need to support in gradle build the same. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17965) Enable remote build cache for Gradle
[ https://issues.apache.org/jira/browse/IGNITE-17965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17965: --- Description: Need to enable remote build cache feature for Gradle on CI. (was: Need to enable remote build cache feature for Gradle for CI. ) > Enable remote build cache for Gradle > > > Key: IGNITE-17965 > URL: https://issues.apache.org/jira/browse/IGNITE-17965 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to enable remote build cache feature for Gradle on CI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17965) Enable remote build cache for Gradle
[ https://issues.apache.org/jira/browse/IGNITE-17965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17965: --- Description: Need to enable remote build cache feature for Gradle for CI. > Enable remote build cache for Gradle > > > Key: IGNITE-17965 > URL: https://issues.apache.org/jira/browse/IGNITE-17965 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > > Need to enable remote build cache feature for Gradle for CI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17965) Enable remote build cache for Gradle
[ https://issues.apache.org/jira/browse/IGNITE-17965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17965: --- Labels: ignite-3 (was: ) > Enable remote build cache for Gradle > > > Key: IGNITE-17965 > URL: https://issues.apache.org/jira/browse/IGNITE-17965 > Project: Ignite > Issue Type: Improvement > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Need to enable remote build cache feature for Gradle for CI. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17965) Enable remote build cache for Gradle
Mikhail Pochatkin created IGNITE-17965: -- Summary: Enable remote build cache for Gradle Key: IGNITE-17965 URL: https://issues.apache.org/jira/browse/IGNITE-17965 Project: Ignite Issue Type: Improvement Components: build Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17901) Fix .NET tests
Mikhail Pochatkin created IGNITE-17901: -- Summary: Fix .NET tests Key: IGNITE-17901 URL: https://issues.apache.org/jira/browse/IGNITE-17901 Project: Ignite Issue Type: Bug Components: build, ignite-3 Reporter: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17901) Fix .NET tests
[ https://issues.apache.org/jira/browse/IGNITE-17901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17901: -- Assignee: Mikhail Pochatkin > Fix .NET tests > -- > > Key: IGNITE-17901 > URL: https://issues.apache.org/jira/browse/IGNITE-17901 > Project: Ignite > Issue Type: Bug > Components: build, ignite-3 >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17862) Restore grade build by adding newly added replicas module to the flow
[ https://issues.apache.org/jira/browse/IGNITE-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17862: --- Component/s: build > Restore grade build by adding newly added replicas module to the flow > - > > Key: IGNITE-17862 > URL: https://issues.apache.org/jira/browse/IGNITE-17862 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Alexander Lapin >Assignee: Mikhail Pochatkin >Priority: Major > > New replicator module, that was added during tx RW implementation, wasn't > added to the gradle build scripts and resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17862) Restore grade build by adding newly added replicas module to the flow
[ https://issues.apache.org/jira/browse/IGNITE-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17862: --- Labels: ignite-3 (was: ) > Restore grade build by adding newly added replicas module to the flow > - > > Key: IGNITE-17862 > URL: https://issues.apache.org/jira/browse/IGNITE-17862 > Project: Ignite > Issue Type: Bug > Components: build >Reporter: Alexander Lapin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > New replicator module, that was added during tx RW implementation, wasn't > added to the gradle build scripts and resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17862) Restore grade build by adding newly added replicas module to the flow
[ https://issues.apache.org/jira/browse/IGNITE-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17862: -- Assignee: Mikhail Pochatkin > Restore grade build by adding newly added replicas module to the flow > - > > Key: IGNITE-17862 > URL: https://issues.apache.org/jira/browse/IGNITE-17862 > Project: Ignite > Issue Type: Bug >Reporter: Alexander Lapin >Assignee: Mikhail Pochatkin >Priority: Major > > New replicator module, that was added during tx RW implementation, wasn't > added to the gradle build scripts and resources. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (IGNITE-17486) Enable Gradle build on CI
[ https://issues.apache.org/jira/browse/IGNITE-17486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin reassigned IGNITE-17486: -- Assignee: Mikhail Pochatkin > Enable Gradle build on CI > - > > Key: IGNITE-17486 > URL: https://issues.apache.org/jira/browse/IGNITE-17486 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Assignee: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > > Start run build verifications for Gradle on CI. > It should be separate verification pipeline with Maven. > IMPORTANT: Maven build scripts should NOT removed in this ticket. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (IGNITE-17781) Create DEB\RPM distributions for CLI
Mikhail Pochatkin created IGNITE-17781: -- Summary: Create DEB\RPM distributions for CLI Key: IGNITE-17781 URL: https://issues.apache.org/jira/browse/IGNITE-17781 Project: Ignite Issue Type: New Feature Components: build, cli Reporter: Mikhail Pochatkin Assignee: Mikhail Pochatkin -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17417) Node name support in CLI
[
https://issues.apache.org/jira/browse/IGNITE-17417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-17417:
---
Description:
Now there is only one way to point at the ignite node in the CLI – `node-url`
or `cluster-url` options. They are represented as an URL that sometimes is too
annoying to type and remember. It would be much more user-friendly to have the
second option here. I think node name could be used as a CLI option.
I propose to add `node-name` option to every command that requires
`cluster-url` or `node-url`. So, the following user story would be possible:
{code:bash}
> ignite
[disconnected]> connect node2
[node2]> connect node2
[node2]> node config show --node-name node1
{code}
was:
Now there is only one way to point at the ignite node in the CLI – `node-url`
or `cluster-url` options. They are represented as an URL that sometimes is too
annoying to type and remember. It would be much more user-friendly to have the
second option here. I think node name could be used as a CLI option.
I propose to add `node-name` option to every command that requires
`cluster-url` or `node-url`. So, the following user story would be possible:
{code:bash}
> ignite
[disconnected]> node start node1
[disconnected]> node start node2
[disconnected]> connect node2
[node2]> connect node2
[node2]> node config show --node-name node1
{code}
> Node name support in CLI
>
>
> Key: IGNITE-17417
> URL: https://issues.apache.org/jira/browse/IGNITE-17417
> Project: Ignite
> Issue Type: Task
> Components: cli
>Reporter: Aleksandr
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> Now there is only one way to point at the ignite node in the CLI – `node-url`
> or `cluster-url` options. They are represented as an URL that sometimes is
> too annoying to type and remember. It would be much more user-friendly to
> have the second option here. I think node name could be used as a CLI option.
> I propose to add `node-name` option to every command that requires
> `cluster-url` or `node-url`. So, the following user story would be possible:
> {code:bash}
> > ignite
> [disconnected]> connect node2
> [node2]> connect node2
> [node2]> node config show --node-name node1
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-17489) Packaging: Brew package
[ https://issues.apache.org/jira/browse/IGNITE-17489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17489: --- Component/s: build > Packaging: Brew package > --- > > Key: IGNITE-17489 > URL: https://issues.apache.org/jira/browse/IGNITE-17489 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17490) Packaging: SDKman package
[ https://issues.apache.org/jira/browse/IGNITE-17490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17490: --- Component/s: build > Packaging: SDKman package > - > > Key: IGNITE-17490 > URL: https://issues.apache.org/jira/browse/IGNITE-17490 > Project: Ignite > Issue Type: New Feature > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3 > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17483) Ignite Packaging improvements
[ https://issues.apache.org/jira/browse/IGNITE-17483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17483: --- Component/s: build > Ignite Packaging improvements > - > > Key: IGNITE-17483 > URL: https://issues.apache.org/jira/browse/IGNITE-17483 > Project: Ignite > Issue Type: Epic > Components: build >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17172) Create new command frontend for REPL mode
[
https://issues.apache.org/jira/browse/IGNITE-17172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-17172:
---
Component/s: cli
> Create new command frontend for REPL mode
> -
>
> Key: IGNITE-17172
> URL: https://issues.apache.org/jira/browse/IGNITE-17172
> Project: Ignite
> Issue Type: Improvement
> Components: cli
>Reporter: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> Currently all commands for both non-REPL and REPL mode has same frontend
> Picocli. It means that options parsing and mapping to command description is
> Picocli relationship.
> Command logic is not related to frontend, relationship of frontend is split
> incoming command line and put all command option to next layer to process
> command execution.
> In reality Picocli frontend for REPL command is not suitable by few reasons:
> # In plans support interactive fill for required options. For example
> {code:java}
> cli> node connect
> Q:Do you want to connect last node? (last-node-url) Y/n?
> A: Y Output:
> Connected to last-node-url! {code}
> Picocli doesn't provide possibility to customize logic about command parsing
> and spliting to options.
> # In current implementation SQL REPL didn't use Picocli frontend because its
> impossible to map all possible SQL queries to different Picocli CmdDesc but
> its is not needed.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16973) Add advanced completions to SQL REPL
[
https://issues.apache.org/jira/browse/IGNITE-16973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Pochatkin updated IGNITE-16973:
---
Component/s: cli
> Add advanced completions to SQL REPL
>
>
> Key: IGNITE-16973
> URL: https://issues.apache.org/jira/browse/IGNITE-16973
> Project: Ignite
> Issue Type: Task
> Components: cli
>Reporter: Aleksandr
>Assignee: Mikhail Pochatkin
>Priority: Major
> Labels: ignite-3, ignite-3-cli-tool
>
> In order to improve the developer experience in SQL REPL mode dynamic
> autocompletion can be added. For example, a user types {{select * from ta}}
> and gets the suggestion with the list of tables that are fetched from the
> JDBC.
> Also, the current list of SQL keywords for autocomplete is taken from the
> default Calcite parser. Use an actual list of Ignite SQL keywords for
> auto-complete.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (IGNITE-16974) Map ignite errors to the command line exit codes
[ https://issues.apache.org/jira/browse/IGNITE-16974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-16974: --- Component/s: cli > Map ignite errors to the command line exit codes > > > Key: IGNITE-16974 > URL: https://issues.apache.org/jira/browse/IGNITE-16974 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Assignee: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Provide the list of errors that can be produced by REST, for example: > * VALIDATION_EXCEPTION > * CONFIG_PATH_UNRECOGNIZED > * INVALID_CONFIG_FORMAT > And map them to CLI exit codes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17484) Tech debt with static context in Question and Cmd providing
[ https://issues.apache.org/jira/browse/IGNITE-17484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17484: --- Component/s: cli > Tech debt with static context in Question and Cmd providing > --- > > Key: IGNITE-17484 > URL: https://issues.apache.org/jira/browse/IGNITE-17484 > Project: Ignite > Issue Type: Improvement > Components: cli >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Currently, org.apache.ignite.cli.core.flow.question.QuestionAskerFactory and > org.apache.ignite.cli.core.repl.context.CommandLineContextProvider has a > static context which should be refactored in non-static model with better > injection logic. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16970) IEP-88: CLI Tool
[ https://issues.apache.org/jira/browse/IGNITE-16970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-16970: --- Component/s: cli > IEP-88: CLI Tool > > > Key: IGNITE-16970 > URL: https://issues.apache.org/jira/browse/IGNITE-16970 > Project: Ignite > Issue Type: Epic > Components: cli >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Develop an advanced CLI Tool with an explicit focus on usability. > A user should download the tool from the website and then use it to: > * Connect to a cluster to monitor its state and perform management > operations (configuration changes, cluster init). > * Connect to a cluster to run SQL queries. > * Connect to a cluster to get the cluster status (topology, version). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17102) Implement cluster show command
[ https://issues.apache.org/jira/browse/IGNITE-17102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17102: --- Component/s: cli > Implement cluster show command > -- > > Key: IGNITE-17102 > URL: https://issues.apache.org/jira/browse/IGNITE-17102 > Project: Ignite > Issue Type: Task > Components: cli >Reporter: Aleksandr >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > Now `cluster show` is an alias for `status` but according to the IEP it > should display wider information. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17170) Drop deprecated package
[ https://issues.apache.org/jira/browse/IGNITE-17170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mikhail Pochatkin updated IGNITE-17170: --- Component/s: cli > Drop deprecated package > > > Key: IGNITE-17170 > URL: https://issues.apache.org/jira/browse/IGNITE-17170 > Project: Ignite > Issue Type: Improvement > Components: cli >Reporter: Mikhail Pochatkin >Priority: Major > Labels: ignite-3, ignite-3-cli-tool > > After migrate to new CLI (IGNITE-16971) to support backward compatibility, > existed commands (cluster/node bootstrap, start, stop ...) moved to > deprecated module. Need to rewrite this commands to new Pipeline architecture > and drop all not needed code. -- This message was sent by Atlassian Jira (v8.20.10#820010)
