You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Kosenchuk (JIRA)" <ji...@apache.org> on 2018/05/10 11:11:00 UTC

[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&focusedCommentId=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)