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] [Comment Edited] (IGNITE-185) Batch mode for Visorcmd
Date Tue, 03 Mar 2015 12:25:05 GMT

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

Vasilisa Sidorova edited comment on IGNITE-185 at 3/3/15 12:24 PM:
-------------------------------------------------------------------

Ubuntu 14.04, Ignate Fabric Only Build #107 for ignite-185 branch (ver. 1.0.1-RC1-SNAPSHOT#20150224-sha1:1ff1c8e6):

Checked for the commands set: "open;3;node;0;y;vvm;kill;0;r;y;y;[exit]" from command line
and from file. It's OK excepting one moment:

If commands set haven't "exit" as last command user stay in the visor session but  couldn't
doing something here only close the terminal.

So, expected result is: if last command in commands set isn't "exit" send  to visorcmd forced
"exit". Please, implement this.






was (Author: vsidorova):
Ubuntu 14.04, Ignate Fabric Only Build #107 for ignite-185 branch (ver. 1.0.1-RC1-SNAPSHOT#20150224-sha1:1ff1c8e6):

Checked for the commands set: "open;3;node;0;y;vvm;kill;0;r;y;y;[exit]" from command line
and from file. It's OK except one moment:

If commands set haven't "exit" as last command user stay in the visor session but  couldn't
doing something here only close the terminal.

So, expected result is: if last command in commands set isn't "exit" send  to visorcmd forced
"exit". Please, implement this.





> 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: Alexey Kuznetsov
>             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
(v6.3.4#6332)

Mime
View raw message