[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483675#comment-16483675
]
ekaterina.vergizova commented on IGNITE-8463:
-
Thanks, we are working on other tests.
123456 is just a keyStore/trustStore password.
ignite/ignite is default username/password for IgniteConfiguration with enabled
authentication and they should be used for activation.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483666#comment-16483666
]
Peter Ivanov commented on IGNITE-8463:
--
Fixed TLS test, others are still failing:
https://ci.ignite.apache.org/viewLog.html?buildId=1320110
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483632#comment-16483632
]
Peter Ivanov commented on IGNITE-8463:
--
Why {{ignite}} if we have {{123456}} in configuration?
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483628#comment-16483628
]
ekaterina.vergizova commented on IGNITE-8463:
-
I activated the cluster with "control.bat --activate --user ignite --password
ignite" command
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483626#comment-16483626
]
Peter Ivanov commented on IGNITE-8463:
--
[~ekaterina.vergizova], how did you activated cluster?
My activation fails with
{code}
bash bin/control.sh --user 123456 --password 123456 --activate
Control utility [ver. 2.5.0-SNAPSHOT#20180517-sha1:83c5423b]
2018 Copyright(C) Apache Software Foundation
User: vveider
Failed to activate cluster.
Authentication error.
Error: Latest topology update failed.
{code}
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483178#comment-16483178
]
ekaterina.vergizova commented on IGNITE-8463:
-
The TLS test is successfully passed locally.
I use the following IgniteConfiguration to run it:
Probably you lose keyStorePassword and trustStorePassword properties and may be
something else.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482669#comment-16482669
]
Peter Ivanov commented on IGNITE-8463:
--
Integrated TLS: https://ci.ignite.apache.org/viewLog.html?buildId=1318038.
Please check that TLS test problem is test failure, not build.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482461#comment-16482461
]
Peter Ivanov commented on IGNITE-8463:
--
[~ekaterina.vergizova], filed IGNITE-8543.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482449#comment-16482449
]
ekaterina.vergizova commented on IGNITE-8463:
-
Seems when the debug was on not all tests were run by TC for unknown reason
(locally all tests are run even with debug). May be TC has some limitations?
Now, with debug off, all tests are run and passed.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482436#comment-16482436
]
Peter Ivanov commented on IGNITE-8463:
--
[~ekaterina.vergizova], some note: after turning debug off, total tests count
increased from
[64|https://ci.ignite.apache.org/viewLog.html?buildId=1316067=buildResultsDiv=IgniteTests24Java8_ThinClientNodeJs]
to
[99|https://ci.ignite.apache.org/viewLog.html?buildId=1316268=buildResultsDiv=IgniteTests24Java8_ThinClientNodeJs].
Is it predicted behaviour?
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482320#comment-16482320
]
Peter Ivanov commented on IGNITE-8463:
--
[~ekaterina.vergizova], turned debug off, log size decreased by 7 times, thanks
for recommendation.
Parameter was left in settings for ability to quickly turn it on on possible
build problems.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482318#comment-16482318
]
ekaterina.vergizova commented on IGNITE-8463:
-
Thanks, I would also recommend not to use APACHE_IGNITE_CLIENT_DEBUG=true
environment var value because it generates too much extra output
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16482274#comment-16482274
]
Peter Ivanov commented on IGNITE-8463:
--
Examples tests integrated:
https://ci.ignite.apache.org/viewLog.html?buildId=1316067
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481518#comment-16481518
]
Alexey Kosenchuk commented on IGNITE-8463:
--
Added executors for examples.
The instruction is updated in
ignite/modules/platforms/nodejs/spec/README.md
Please integrate them as well. Thanks.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480818#comment-16480818
]
Alexey Kosenchuk commented on IGNITE-8463:
--
Tests updated - the required output added.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477520#comment-16477520
]
Peter Ivanov commented on IGNITE-8463:
--
Build configuration is set: [Ignite Tests 2.4+ (Java 8) / Thin client:
Node.js|https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_ThinClientNodeJs]
However TeamCity does not support test reporting for Jasmine tests, thus
something like this https://gist.github.com/shamansir/3497509 should be added /
implemented for TC reporting.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471270#comment-16471270
]
Alexey Kosenchuk commented on IGNITE-8463:
--
Please use the latest PR with the full API
https://github.com/apache/ignite/pull/3978
Test instructions are in a separate readme now:
ignite/modules/platforms/nodejs/spec/README.md
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.6
>
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470223#comment-16470223
]
Alexey Kosenchuk commented on IGNITE-8463:
--
"npm test" from the root folder of the nodejs client - as described in the
readme.
There should be no more requirements for the environment additional to the npm.
Please let us know, if it's not true.
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.6
>
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
[
https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16470190#comment-16470190
]
Vladimir Ozerov commented on IGNITE-8463:
-
[~alexey.kosenchuk], could you please provide a command to start Jasmine tests
from console?
> Node.js: setup TeamCity
> ---
>
> Key: IGNITE-8463
> URL: https://issues.apache.org/jira/browse/IGNITE-8463
> Project: Ignite
> Issue Type: Sub-task
> Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.6
>
>
> Minimal implementation of NodeJS client is almost ready (IGNITE-8014). We
> need to figure out how to integrate it with TeamCity:
> 1) New suite for NodeJS is needed along with required environment (npm, any
> recent version). 2) Suite should be able to run Jasmine tests [1]
> 3) Currently all tests rely on manually started external node. We need to
> create a set of scripts (bash?) to start/stop nodes locally from Jasmine. Raw
> suggestion: call {{ignite.sh}} with predefined configuration.
> [1] https://jasmine.github.io/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
