ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vasilisa Sidorova (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-185) Batch mode for Visorcmd
Date Thu, 05 Mar 2015 11:52:38 GMT

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

Vasilisa Sidorova commented on IGNITE-185:

Ubuntu 14.04, Ignate Fabric Only Build #118 for ignite-185 branch (ver. 1.0.0-RC2-SNAPSHOT#20150305-sha1:0149a0d3):

Now all is works correctly. Thanks.

Windows 7, Ignate Fabric Only Build #114 for ignite-185 branch (ver. 1.0.0-RC2-SNAPSHOT#20150304-sha1:e9356ab0):

1) There is OK for input commands set from command line
2) There is problem with input commands set from file: the numbers and letters which are answers
are read as independent commands. Look at the command's "ignitevisorcmd.bat -b=withExit" results
in the file "runVisorcmdWithFileResults". Input file "withExit" is also attached

> Batch mode for Visorcmd
> -----------------------
>                 Key: IGNITE-185
>                 URL: https://issues.apache.org/jira/browse/IGNITE-185
>             Project: Ignite
>          Issue Type: Task
>          Components: UI
>    Affects Versions: sprint-1
>            Reporter: Alexey Kuznetsov
>            Assignee: Vasilisa Sidorova
>             Fix For: sprint-2
> Batch mode for visorcmd allow to read commands from test file (one command per line),
perform them, send output to STDOUT/STDERR and exit if end of text file has been reached.
> e.g. ./bin/ggvisorcmd -b path_to_batch_file
> For this case the output of visorcmd will be stored into the file and test scripts can
compare content of this file against expected result.
> Expected troubles for implementing is requests of confirmation/parameters for some commands
(e.g. "kill" - confirm to kill, "open" - set number of config file). But can be resolved by
following ways:
> next line after such command contains text for request, e.g.
> open 
> 14
> kill
> y
> after command inside brackets we put text for request
> open {14}
> kill
> {y}
> do not ask confirmation if visorcmd started in batch mode (but how to resolve commands
like "open"?)

This message was sent by Atlassian JIRA

View raw message