Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
I don’t see the donator desire here. This desire is to give AI consumers more frequent releases with bug fix and understanding when we, as a community, will release new, announced features to them. Now it’s not clear why consumers should fix bugs themselves, if they don’t have the opportunity to get the expected delivery time. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Apache Ignite 2.8.1 RELEASE [Time, Scope, Manager]
Hi, Igniters! I propose to discuss immediately the timing of 2.9.0 and interim releases! My propose: ~ June 01 - 2.8.1 ~ September 01 - 2.8.2 ~ November 01 - 2.9.0 Sberbank team, for its part, is ready to take on the work of management interim releases. Regards, Aleksey Chetaev. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[jira] [Created] (IGNITE-7594) Tx performance drop after WAL optimization
Aleksey Chetaev created IGNITE-7594: --- Summary: Tx performance drop after WAL optimization Key: IGNITE-7594 URL: https://issues.apache.org/jira/browse/IGNITE-7594 Project: Ignite Issue Type: Bug Affects Versions: 2.4 Reporter: Aleksey Chetaev Perfomance dropes in tx-putAll benchmarks after commit with WAL optimization. First bad commit: https://github.com/apache/ignite/commit/a5ffd4eb18e6e9eab30c176a7bb4008a51b3d59d -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-7094) Javadoc warnings in ml module
Aleksey Chetaev created IGNITE-7094: --- Summary: Javadoc warnings in ml module Key: IGNITE-7094 URL: https://issues.apache.org/jira/browse/IGNITE-7094 Project: Ignite Issue Type: Bug Components: ml Affects Versions: 2.4 Reporter: Aleksey Chetaev [14:20:11][Step 18/41] [WARNING] Javadoc Warnings [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link:illegal character: "47" in "/*SparseDistributedVector" [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link:illegal character: "42" in "/*SparseDistributedVector" [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/math/impls/storage/vector/SparseDistributedVectorStorage.java:43: warning - Tag @link: reference not found: /*SparseDistributedVector [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/ContinuousSplitCalculator.java:37: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:39: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/CacheColumnDecisionTreeTrainerInput.java:82: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apache/ignite/ml/trees/trainers/columnbased/ColumnDecisionTreeTrainerInput.java:28: warning - Tag @see cannot be used in inline documentation. It can only be used in the following types of documentation: overview, package, class/interface, constructor, field, method. [14:20:11][Step 18/41] [WARNING] /var/lib/teamcity/data/work/6ae9d4bd0822354f/incubator-ignite/modules/ml/src/main/java/org/apa
[jira] [Created] (IGNITE-6822) IgfsMapReduceExample raise exception in multi nodes run
Aleksey Chetaev created IGNITE-6822:
---
Summary: IgfsMapReduceExample raise exception in multi nodes run
Key: IGNITE-6822
URL: https://issues.apache.org/jira/browse/IGNITE-6822
Project: Ignite
Issue Type: Bug
Security Level: Public (Viewable by anyone)
Reporter: Aleksey Chetaev
Priority: Minor
All logs in attachments.
Exception:
{code:java}
class org.apache.ignite.internal.IgniteInterruptedCheckedException: sleep
interrupted
at org.apache.ignite.internal.util.IgniteUtils.sleep(IgniteUtils.java:7538)
at
org.apache.ignite.internal.MarshallerMappingFileStore.fileLock(MarshallerMappingFileStore.java:254)
at
org.apache.ignite.internal.MarshallerMappingFileStore.writeMapping(MarshallerMappingFileStore.java:95)
at org.apache.ignite.internal.MappingStoreTask.run(MappingStoreTask.java:57)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6687)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
Re: Check Ignite build for different Java before VOTE
Dmitriy, Sorry, we had problem on Ignite TeamCity, I fixed it, now project available for all developers. Dmitry Pavlov wrote > Hi Aleksey, > > I think all types of release automation is very good for improving our > processes and provide stable product. > > Currently I am not able to view new Run configs: > You do not have enough permissions to access build type with id: > IgniteRelease_427CheckBuildIgniteFabricOpenJDK8 > > What should I do to see new builds? > > Sincerely, > Dmitriy Pavlov > > ср, 6 сент. 2017 г. в 15:57, Aleksey Chetaev > alex.chetaev@ > : > >> Igniters, >> >> In Ignite DEVNOTES we have full instruction how we can build Ignite, but >> we >> have a lot of different options with which Ignite can be builded: >> 1. Ignite Fabric without Scala modules >> 2. Ignite Fabric with Scala modules >> 3. Ignite Fabric LGPL without Scala >> 4. Ignite Fabric LGPL with Scala >> 5. Ignite Hadoop for default Hadoop release. >> 6. Ignite Hadoop for one of last Hadoop release >> 7. Ignite Hadoop for one of last Hadoop version and one of Spark >> version. >> Because we provide source code to users, success build for all this >> options >> should be tested with all supported Java version before release. Make it >> manually it's really difficult. >> >> So that release developer can check all this build option automatically I >> created 9 task on TeamCity. All task download source archive from svn for >> release candidate using params and start build on downloaded source. (now >> source downloading from release svn for testing, because release >> candidate >> svn is empty) >> >> 1. Task check that we have license headers in all source files: >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_41CheckLicenseHeadersInFiles >> 2. Tasks check build option 1-4 for Oracle Java 7,8 and for OpenJDK 7,8: >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_421CheckBuildIgniteFabricOracleJava7 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_423CheckBuildIgniteFabricOracleJava8 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_425CheckBuildIgniteFabricOpenJDK7 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_427CheckBuildIgniteFabricOpenJDK8 >> 3. Tasks check build option 5-7 for Oracle Java 7,8 and for OpenJDK 7,8, >> for Hadoop(default, 2.6.5, 2.7.3) and for Spark(2.1.1, 2.2.0) >>* >> >> https://ci.ignite.apache.org/viewLog.html?buildId=811586=buildResultsDiv=IgniteRelease_422CheckBuildIgniteHadoopOracleJava7 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_424CheckBuildIgniteHadoopOracleJava8 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_426CheckBuildIgniteHadoopOpenJDK7 >>* >> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_428CheckBuildIgniteHadoopOpenJDK8 >> >> I think we should change release process and release developer should run >> all this task before send release to VOTE. >> >> >> >> >> >> >> >> >> -- >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ >> -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Check Ignite build for different Java before VOTE
FYI: I founded some issues with build failed in our JIRA: 1. https://issues.apache.org/jira/browse/IGNITE-2149 2. https://issues.apache.org/jira/browse/IGNITE-4721 -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Check Ignite build for different Java before VOTE
Igniters, In Ignite DEVNOTES we have full instruction how we can build Ignite, but we have a lot of different options with which Ignite can be builded: 1. Ignite Fabric without Scala modules 2. Ignite Fabric with Scala modules 3. Ignite Fabric LGPL without Scala 4. Ignite Fabric LGPL with Scala 5. Ignite Hadoop for default Hadoop release. 6. Ignite Hadoop for one of last Hadoop release 7. Ignite Hadoop for one of last Hadoop version and one of Spark version. Because we provide source code to users, success build for all this options should be tested with all supported Java version before release. Make it manually it's really difficult. So that release developer can check all this build option automatically I created 9 task on TeamCity. All task download source archive from svn for release candidate using params and start build on downloaded source. (now source downloading from release svn for testing, because release candidate svn is empty) 1. Task check that we have license headers in all source files: https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_41CheckLicenseHeadersInFiles 2. Tasks check build option 1-4 for Oracle Java 7,8 and for OpenJDK 7,8: * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_421CheckBuildIgniteFabricOracleJava7 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_423CheckBuildIgniteFabricOracleJava8 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_425CheckBuildIgniteFabricOpenJDK7 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_427CheckBuildIgniteFabricOpenJDK8 3. Tasks check build option 5-7 for Oracle Java 7,8 and for OpenJDK 7,8, for Hadoop(default, 2.6.5, 2.7.3) and for Spark(2.1.1, 2.2.0) * https://ci.ignite.apache.org/viewLog.html?buildId=811586=buildResultsDiv=IgniteRelease_422CheckBuildIgniteHadoopOracleJava7 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_424CheckBuildIgniteHadoopOracleJava8 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_426CheckBuildIgniteHadoopOpenJDK7 * https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteRelease_428CheckBuildIgniteHadoopOpenJDK8 I think we should change release process and release developer should run all this task before send release to VOTE. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
[jira] [Created] (IGNITE-6243) RazorSQL crashed on try edit, describe and another actions with table.
Aleksey Chetaev created IGNITE-6243: --- Summary: RazorSQL crashed on try edit, describe and another actions with table. Key: IGNITE-6243 URL: https://issues.apache.org/jira/browse/IGNITE-6243 Project: Ignite Issue Type: Bug Components: odbc Affects Versions: 2.1 Reporter: Aleksey Chetaev 1. Install ODBC on Windows. 2. Crete DSN for Ignite ODBC Driver. 3. Connect by RazorSQL using ODBC. 4. Create new table. 5. Try to edit table, using right click. RazorSQL crashed without error. Need check that it's not crash of Apache Ignite ODBC driver. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6189) Benchmarks for check LFS used disk space
Aleksey Chetaev created IGNITE-6189: --- Summary: Benchmarks for check LFS used disk space Key: IGNITE-6189 URL: https://issues.apache.org/jira/browse/IGNITE-6189 Project: Ignite Issue Type: Improvement Reporter: Aleksey Chetaev Need to create new benchmarks for test how many space we use for store n keys in LFS. Benchmark should content arguments: 1. Range of entries which will be put. 2. How often we show store size. Case for e.x. params (range 1_000_000, step 100_000): 1. Put 100_000 entries, save time for put 2. Wait for checkpoint finished on all nodes. 3. Calc db size on each server. 4. Write size and time to benchmarks results. ... 6. Repeat first 4 steps while entries count in cache less that 1_000_000. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (IGNITE-6108) Hangs in streamer when using store
Aleksey Chetaev created IGNITE-6108: --- Summary: Hangs in streamer when using store Key: IGNITE-6108 URL: https://issues.apache.org/jira/browse/IGNITE-6108 Project: Ignite Issue Type: Bug Affects Versions: 2.1 Reporter: Aleksey Chetaev Priority: Critical I have hangs in IgniteStreamer benchmarks when using store with WAL mode different from NONE. Configuration: 1 client 4 servers.Cache mode: transaction. Range 400_000_000. Problems: * Time for next 100_000_000 entries every is always greater than for the previous one. * We can found hangs for greater that 1 minutes in drivers logs for example 11:47:21 - 11:48:27 in archive named "log_with_memory_policy". Yardstick logs in attachments. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: SSL certificate for the CI server
If anyone can’t sleep at night If anyone sleep very bad If you afraid that your password Can evil hacker steal right now For they we worked day and night Don’t slept and worked fully days And finish with https Teamcity for, Igniters for. https://ci.ignite.apache.org -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p20532.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: Release notes tools for Ignite releases
If the solution is positive, can anyone see my pull request? 2017-08-03 4:28 GMT+03:00 dsetrakyan [via Apache Ignite Developers] < ml+s2346864n20403...@n4.nabble.com>: > Agree with Denis. I think that we should treat it as a starting point for > the release notes, and further update it before releases. > > On Wed, Aug 2, 2017 at 10:58 PM, Denis Magda <[hidden email] > <http:///user/SendEmail.jtp?type=node=20403=0>> wrote: > > > Guys, > > > > We're on the same page that the page has to look more colorful and > > informative. This is exactly why Spark's page was given as an example. > > > > However, I like the template generated by Alex script in a sense that > you > > already have something to start work with. Go ahead and remove redundant > > tickets once the template is ready, apply CSS and other nice formatting, > > etc. So I would still accept the contribution. > > > > Denis > > > > On Wednesday, August 2, 2017, Vladimir Ozerov <[hidden email] > <http:///user/SendEmail.jtp?type=node=20403=1>> > > wrote: > > > > > Alex, > > > > > > This is not only about the issue types. Release notes is the face of > our > > > product. Generating it from JIRA has several problems which are > > > unresolvable IMO: > > > 1) Tickets are created by many dozens people, so there could be typos, > > > linguistic errors, etc. > > > 2) Ticket descriptions often inconclusive and gives no useful > information > > > to users > > > > > > The only way to have sensible Release notes is to create them > manually. > > > Instead of forcing many people to follow some rules just to make this > > > report looks sexy, we'd better to have one responsbile enginner, who > will > > > spend an hour once in 1-2 months to make release notes correct and > > > meaningful. We can have a template with , , , tags > for > > > nice markup. > > > > > > > > > On Wed, Aug 2, 2017 at 10:55 PM, Aleksey Chetaev <[hidden email] > <http:///user/SendEmail.jtp?type=node=20403=2> > > > <javascript:;>> > > > wrote: > > > > > > > Vladimir, > > > > > > > > I agree that page not perfect now. I think, problem in Jira issue > > types. > > > A > > > > lot of new features or improvements created as task and often we > don't > > > use > > > > sub-task for depended issues. I can be wrong, but committer who > > prepared > > > > release can't manually create this page, we need have some tools. > > > > > > > > 2017-08-02 21:35 GMT+03:00 Vladimir Ozerov [via Apache Ignite > > > Developers] < > > > > [hidden email] <http:///user/SendEmail.jtp?type=node=20403=3> > <javascript:;>>: > > > > > > > > > JIRA = report from JIRA > > > > > > > > > > ср, 2 авг. 2017 г. в 21:35, Vladimir Ozerov <[hidden email] > > > > > <http:///user/SendEmail.jtp?type=node=20398=0>>: > > > > > > > > > > > Denis, > > > > > > > > > > > > This page works exactly how I suggested in the beginning of that > > > > thread: > > > > > > manually crafted notes on most important features + link to JIRA > > > report > > > > > to > > > > > > see all closed tickets. > > > > > > > > > > > > We already have manually crafted any properly grouped release > > notes. > > > > All > > > > > > we need is to make them a bit more verbose, add some CSS and > > publish > > > on > > > > > the > > > > > > site. No need to publish JIRA, this is useless noise. > > > > > > > > > > > > ср, 2 авг. 2017 г. в 21:20, Denis Magda <[hidden email] > > > > > <http:///user/SendEmail.jtp?type=node=20398=1>>: > > > > > > > > > > > >> Vladimir, > > > > > >> > > > > > >> The goal is to have a page like that: > > > > > >> https://spark.apache.org/releases/spark-release-2-1-0.html < > > > > > >> https://spark.apache.org/releases/spark-release-2-1-0.html> > > > > > >> > > > > > >> where a user can go and see all the changes incorporated in the > > > > > release. > > > > > >> The header of the file can
[jira] [Created] (IGNITE-5920) CacheClientBinaryQueryExample return different results if we add non local node
Aleksey Chetaev created IGNITE-5920: --- Summary: CacheClientBinaryQueryExample return different results if we add non local node Key: IGNITE-5920 URL: https://issues.apache.org/jira/browse/IGNITE-5920 Project: Ignite Issue Type: Bug Reporter: Aleksey Chetaev 1. Start CacheClientBinaryQueryExample without external nodes. Section ">>> Employees working for GridGain" isn't empty. 2. Start 3 node and after that start example. section ">>> Employees working for GridGain" is empty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
Re: Release notes tools for Ignite releases
Vladimir, I agree that page not perfect now. I think, problem in Jira issue types. A lot of new features or improvements created as task and often we don't use sub-task for depended issues. I can be wrong, but committer who prepared release can't manually create this page, we need have some tools. 2017-08-02 21:35 GMT+03:00 Vladimir Ozerov [via Apache Ignite Developers] < ml+s2346864n20398...@n4.nabble.com>: > JIRA = report from JIRA > > ср, 2 авг. 2017 г. в 21:35, Vladimir Ozerov <[hidden email] > <http:///user/SendEmail.jtp?type=node=20398=0>>: > > > Denis, > > > > This page works exactly how I suggested in the beginning of that thread: > > manually crafted notes on most important features + link to JIRA report > to > > see all closed tickets. > > > > We already have manually crafted any properly grouped release notes. All > > we need is to make them a bit more verbose, add some CSS and publish on > the > > site. No need to publish JIRA, this is useless noise. > > > > ср, 2 авг. 2017 г. в 21:20, Denis Magda <[hidden email] > <http:///user/SendEmail.jtp?type=node=20398=1>>: > > > >> Vladimir, > >> > >> The goal is to have a page like that: > >> https://spark.apache.org/releases/spark-release-2-1-0.html < > >> https://spark.apache.org/releases/spark-release-2-1-0.html> > >> > >> where a user can go and see all the changes incorporated in the > release. > >> The header of the file can be custom - you can list major achievements > with > >> extra explanation. Going forward we can improve the page layout, design > and > >> content but we definitely need a page like that so that the users can > see > >> the changes without a release download and lookup of RELEASE_NOTES.txt > >> (which is not that descriptive as well). > >> > >> — > >> Denis > >> > >> > On Aug 2, 2017, at 8:36 AM, Vladimir Ozerov <[hidden email] > <http:///user/SendEmail.jtp?type=node=20398=2>> > >> wrote: > >> > > >> > Alex, > >> > > >> > In AI 2.1 we fixed several hundreds issues. Why do you think there is > a > >> > single person interested in reviewing all of them? E.g. we added new > >> JDBC > >> > driver. I do not see it in the list of major features, neither I need > to > >> > know that this task was split into 20 smaller sub tasks, each of > which > >> are > >> > listed in the report. > >> > > >> > The question stands still - who needs this kind of detalization? > >> > > >> > ср, 2 авг. 2017 г. в 17:48, Aleksey Chetaev <[hidden email] > <http:///user/SendEmail.jtp?type=node=20398=3>>: > >> > > >> >> Vladimir, > >> >> > >> >> We have links to release notes on download page: > >> >> https://ignite.apache.org/ > >> >> download.cgi. For be user-friendly we added header with description > >> about > >> >> most interested features in release and near list of issues. If we > want > >> >> skip minor or another issues we can use Jira labels and skip issues > >> with > >> >> label like "skip_rn" using filters, but I don't think it's good way. > >> Users > >> >> shouldn't like use Jira and another developers tools, they want see > >> all new > >> >> (include all fixed) in release and this page easy way to do it. > >> >> > >> >> 2017-08-02 17:09 GMT+03:00 Vladimir Ozerov [via Apache Ignite > >> Developers] < > >> >> [hidden email] <http:///user/SendEmail.jtp?type=node=20398=4>>: > > >> >> > >> >>> Alex. > >> >>> > >> >>> How are we supposed to use this report? Release notes should be > >> designed > >> >>> in > >> >>> such a way, that the most important features are highly visible, > while > >> >>> minor changes are either skipped at all, or shown aside, as they > have > >> >>> little to no value for users. If someone is interested in all fixed > >> >>> tickets, we can give a link to JIRA report. Moreover, some fixes > must > >> be > >> >>> even hidden from users, e.g. security-related stuff. > >> >>> > >> >>> That said, I am not quite sure I understand the purpose of this > >
Re: Release notes tools for Ignite releases
Vladimir, We have links to release notes on download page: https://ignite.apache.org/ download.cgi. For be user-friendly we added header with description about most interested features in release and near list of issues. If we want skip minor or another issues we can use Jira labels and skip issues with label like "skip_rn" using filters, but I don't think it's good way. Users shouldn't like use Jira and another developers tools, they want see all new (include all fixed) in release and this page easy way to do it. 2017-08-02 17:09 GMT+03:00 Vladimir Ozerov [via Apache Ignite Developers] < ml+s2346864n20380...@n4.nabble.com>: > Alex. > > How are we supposed to use this report? Release notes should be designed > in > such a way, that the most important features are highly visible, while > minor changes are either skipped at all, or shown aside, as they have > little to no value for users. If someone is interested in all fixed > tickets, we can give a link to JIRA report. Moreover, some fixes must be > even hidden from users, e.g. security-related stuff. > > That said, I am not quite sure I understand the purpose of this reporting. > It is not user-friendly. > > Vladimir. > > On Wed, Aug 2, 2017 at 4:57 PM, Aleksey Chetaev <[hidden email] > <http:///user/SendEmail.jtp?type=node=20380=0>> > wrote: > > > Igniters, > > > > Started 2.0 we generated manually Jira based release notes with all new > > improvements and fixed bugs. > > f.e(https://ignite.apache.org/releases/2.1.0/release_notes.html). I > > created > > new class in ignite-tools for we can do it automatically using IDE or > > TeamCity. Class using JSON template for create release notes. In > template > > we > > can setup Jira servers with credentials and filters for each release > notes > > section. > > Please see pull request: https://github.com/apache/ignite/pull/2379 may > be > > we can merge this to Ignite for improve our release process? > > > > Kind regards > > Aleksey Chetaev. > > > > > > > > -- > > View this message in context: http://apache-ignite- > > developers.2346864.n4.nabble.com/Release-notes-tools-for- > > Ignite-releases-tp20377.html > > Sent from the Apache Ignite Developers mailing list archive at > Nabble.com. > > > > > -- > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-developers.2346864.n4.nabble.com/Releas > e-notes-tools-for-Ignite-releases-tp20377p20380.html > To unsubscribe from Release notes tools for Ignite releases, click here > <http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=20377=YWxleC5jaGV0YWV2QGdtYWlsLmNvbXwyMDM3N3wtMTkzNjgwOTg1OQ==> > . > NAML > <http://apache-ignite-developers.2346864.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Release-notes-tools-for-Ignite-releases-tp20377p20384.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Release notes tools for Ignite releases
Igniters, Started 2.0 we generated manually Jira based release notes with all new improvements and fixed bugs. f.e(https://ignite.apache.org/releases/2.1.0/release_notes.html). I created new class in ignite-tools for we can do it automatically using IDE or TeamCity. Class using JSON template for create release notes. In template we can setup Jira servers with credentials and filters for each release notes section. Please see pull request: https://github.com/apache/ignite/pull/2379 may be we can merge this to Ignite for improve our release process? Kind regards Aleksey Chetaev. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Release-notes-tools-for-Ignite-releases-tp20377.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: SSL certificate for the CI server
Konstantin, Ok, no objections from my side. I need some times for read documentation. I hope we will finished in two weeks. http://reviews.ignite.apache.org - will setup for ssl using too. Konstantin Boudnik-2 wrote > I have never heard about this provider, and it is great they are donating > their resources to the FOSS. I quick glance on their site has reveiled a > couple of issues: > - the page for the "Standard Agreement" returns 404 [1]. I won't be > willing to > agree to something I cannot read upfront. > - the process seems to be manual. > > The reason I like [2] is because it's backed by EFF and has a huge user > base > (over 100 millions certificates to date) [3] > > The process has been debugged already for other Apache projects, so I > don't > really see why we need to go to someone else? > > [1] > https://www.globalsign.com/en/repository/globalsign-subscriber-agreement-digital-certificates-and-services.pdf > [2] https://letsencrypt.org/ > [3] > https://www.eff.org/deeplinks/2017/06/lets-encrypt-has-issued-100-million-certificates > > Thanks, > Cos > > On Wed, Jul 19, 2017 at 09:41PM, Aleksey Chetaev wrote: >> Hi, >> >> A know GlobalSing support open source projects for >> free(https://www.globalsign.com/en/ssl/ssl-open-source/). >> We can request certificates from them, it will be more easy for me. Any >> objection? >> >> >> Denis Magda-2 wrote >> > Hi Cos, >> > >> > Alexey Chetaev, please join the conversation and share your thoughts on >> > this. >> > >> > — >> > Denis >> > >> >> On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik >> >> > cos@ >> >> > wrote: >> >> >> >> Hey guys. >> >> >> >> I've noticed that https://ci.ignite.apache.org/ has two issues: >> >> - it has the invalid certificate >> >> - the CI server isn't responding on the https port (there's only >> ngnix) >> >> >> >> I don't about the rest of the group here, but all my browsers are >> >> enforcing >> >> HTTPS connections for the obvious reasons. I have to add an exception >> >> for the CI server to get in, which is a minor inconvenience compared >> to >> >> the >> >> security risks. I suggest we fix both issues. >> >> 1. Getting a valid certificate is easy and doesn't cost a dime >> nowadays. >> >> Here's the very details set of instructions on how we do it for >> Apache >> >> Bigtop. They are easily applicable in Ignite CI's case [1]. I'd be >> >> happy to >> >> help with this. >> >> 2. Reconfiguring the server to respond only on HTTPS port. That's >> another >> >> easy >> >> thing to do for anyone with the access to the box. I don't have >> this, >> >> so >> >> it'd be someone else. >> >> >> >> Thoughts? >> >> Cos >> >> >> >> [1] >> >> >> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide#BigtopCISetupGuide-Advancedpart:SetupaSSLsecuredJenkinsmaster >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p19840.html >> Sent from the Apache Ignite Developers mailing list archive at >> Nabble.com. > > > signature.asc (237 bytes) > http://apache-ignite-developers.2346864.n4.nabble.com/attachment/19933/0/signature.asc; -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p20066.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: SSL certificate for the CI server
Hi, A know GlobalSing support open source projects for free(https://www.globalsign.com/en/ssl/ssl-open-source/). We can request certificates from them, it will be more easy for me. Any objection? Denis Magda-2 wrote > Hi Cos, > > Alexey Chetaev, please join the conversation and share your thoughts on > this. > > — > Denis > >> On Jul 19, 2017, at 9:44 AM, Konstantin Boudnik > cos@ > wrote: >> >> Hey guys. >> >> I've noticed that https://ci.ignite.apache.org/ has two issues: >> - it has the invalid certificate >> - the CI server isn't responding on the https port (there's only ngnix) >> >> I don't about the rest of the group here, but all my browsers are >> enforcing >> HTTPS connections for the obvious reasons. I have to add an exception >> for the CI server to get in, which is a minor inconvenience compared to >> the >> security risks. I suggest we fix both issues. >> 1. Getting a valid certificate is easy and doesn't cost a dime nowadays. >> Here's the very details set of instructions on how we do it for Apache >> Bigtop. They are easily applicable in Ignite CI's case [1]. I'd be >> happy to >> help with this. >> 2. Reconfiguring the server to respond only on HTTPS port. That's another >> easy >> thing to do for anyone with the access to the box. I don't have this, >> so >> it'd be someone else. >> >> Thoughts? >> Cos >> >> [1] >> https://cwiki.apache.org/confluence/display/BIGTOP/Bigtop+CI+Setup+Guide#BigtopCISetupGuide-Advancedpart:SetupaSSLsecuredJenkinsmaster >> -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/SSL-certificate-for-the-CI-server-tp19830p19840.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
Re: [ignite] your /dist/ artifacts - 1 BAD signature
Guys, I removed test binaries. I hope Ilya S. can give more comments about this issue on Monday. Best Regards, Aleksey Chetaev. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/Fwd-ignite-your-dist-artifacts-1-BAD-signature-tp19732p19741.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
[jira] [Created] (IGNITE-5434) Yardstick sql benchmarks broken on Ignite-5267 branch
Aleksey Chetaev created IGNITE-5434: --- Summary: Yardstick sql benchmarks broken on Ignite-5267 branch Key: IGNITE-5434 URL: https://issues.apache.org/jira/browse/IGNITE-5434 Project: Ignite Issue Type: Bug Components: sql, yardstick Affects Versions: 2.1 Reporter: Aleksey Chetaev Priority: Critical Yardstick benchmarks: *sql-query *sql-query-join *sql-query-put broken in Ignite-5267 branch, in master all ok. Exception: <00:39:22> Starting warmup. Finishing main test [ts=1496795962893, date=Wed Jun 07 00:39:22 UTC 2017] ERROR: Shutting down benchmark driver to unexpected exception. Type '--help' for usage. javax.cache.CacheException: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:807) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.executeQuery(IgniteSqlQueryBenchmark.java:90) at org.apache.ignite.yardstick.cache.IgniteSqlQueryBenchmark.test(IgniteSqlQueryBenchmark.java:64) at org.yardstickframework.impl.BenchmarkRunner$2.run(BenchmarkRunner.java:178) at java.lang.Thread.run(Thread.java:745) Caused by: class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to parse query: SELECT "query"."Person"._KEY, "query"."Person"._VAL FROM "query"."Person" WHERE salary >= ? and salary <= ? at org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1291)
CI Server permissions changed
Hi, That all users don't be admins, I changed permissions scheme on CI server (http://ci.ignite.apache.org) We have four groups: > TeamCity Admins - group for committers. Users in this group have full access permission to CI server and can add new users. > Ignite Tests Admins - groups for guys, who was in admins group but don't in committers list. This group have admin access to all projects with tests, can create, edit and start builds with test. > Ignite Release Managers - group which have access to release project. > All Users - groups which content all CI server users. Users in this group can start and stop builds in projects with Ignite tests. (Users add to this group automaticly on created). Best Regards, Aleksey Chetaev. -- View this message in context: http://apache-ignite-developers.2346864.n4.nabble.com/CI-Server-permissions-changed-tp18500.html Sent from the Apache Ignite Developers mailing list archive at Nabble.com.
[jira] [Created] (IGNITE-5355) Create task with release tools
Aleksey Chetaev created IGNITE-5355: --- Summary: Create task with release tools Key: IGNITE-5355 URL: https://issues.apache.org/jira/browse/IGNITE-5355 Project: Ignite Issue Type: Task Components: documentation Reporter: Aleksey Chetaev Fix For: 2.1 1. Create task for auto-generate HTML formatted releases notes -- This message was sent by Atlassian JIRA (v6.3.15#6346)
