[jira] [Comment Edited] (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 edited comment on IGNITE-8463 at 5/22/18 8:11 AM:
---
[~ekaterina.vergizova], how did you activate 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}
with no error in node's log.
was (Author: vveider):
[~ekaterina.vergizova], how did you activate 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] [Comment Edited] (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 edited comment on IGNITE-8463 at 5/22/18 8:10 AM:
---
[~ekaterina.vergizova], how did you activate 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}
was (Author: vveider):
[~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] [Comment Edited] (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 edited comment on IGNITE-8463 at 5/22/18 8:10 AM:
---
[~ekaterina.vergizova], how did you activate 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}
was (Author: vveider):
[~ekaterina.vergizova], how did you activate 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] [Comment Edited] (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 edited comment on IGNITE-8463 at 5/21/18 7:52 AM:
---
Examples tests integrated:
https://ci.ignite.apache.org/viewLog.html?buildId=1316067
Waiting for support in configuring ignite node in auth tls mode.
was (Author: vveider):
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] [Comment Edited] (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 edited comment on IGNITE-8463 at 5/10/18 11:10 AM:
"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
and the environment variables described in the readme.
Please let us know, if it's not true.
was (Author: alexey.kosenchuk):
"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)
