ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Kozlov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-185) Batch mode for Visorcmd
Date Fri, 06 Mar 2015 11:22:38 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sergey Kozlov resolved IGNITE-185.
    Resolution: Fixed

> 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: Andrey Novikov
>             Fix For: sprint-2
>         Attachments: runVisorcmdWithFileResults, runVisorcmdWithUTF16FileResults, withExit,
withExit_akelpad_UTF16, withoutExit_UTF16.txt
> 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