ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Ivanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8463) Node.js: setup TeamCity
Date Tue, 22 May 2018 08:11:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483626#comment-16483626

Peter Ivanov commented on IGNITE-8463:

[~ekaterina.vergizova], how did you activated cluster?
My activation fails with
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.

> 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

View raw message