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 Wed, 04 Mar 2015 14:43:05 GMT

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

Vasilisa Sidorova edited comment on IGNITE-185 at 3/4/15 2:42 PM:
------------------------------------------------------------------

Ubuntu 14.04, Ignate Fabric Only Build #114 for ignite-185 branch (ver. 1.0.0-RC2-SNAPSHOT#20150304-sha1:e9356ab0):
--------------------------------------------------------
Now ./ignitevisorcmd.sh doesn't start yet with next errors:

isla@isla:~/Ignite/sp2/ignite-fabric-1.0.0-RC2-SNAPSHOT/bin$ ./ignitevisorcmd.sh 
./ignitevisorcmd.sh: line 35: /home/isla/Ignite/sp2/bin/include/functions.sh: No such file
or directory
./ignitevisorcmd.sh: line 40: checkJava: command not found
./ignitevisorcmd.sh: line 45: setIgniteHome: command not found
./ignitevisorcmd.sh: line 50: /home/isla/Ignite/sp2/bin/include/parseargs.sh: No such file
or directory
./ignitevisorcmd.sh: line 55: /home/isla/Ignite/sp2/bin/include/setenv.sh: No such file or
directory
./ignitevisorcmd.sh: line 119: : command not found
isla@isla:~/Ignite/sp2/ignite-fabric-1.0.0-RC2-SNAPSHOT/bin$ 

--------------------------------------------------------
The results of diff command between new and old scripts is:

26c26
<     then IGNITE_HOME_TMP="$(dirname "$(cd "$(dirname "$0")"; "pwd")")";IGNITE_HOME_TMP="$(dirname
"${IGNITE_HOME_TMP}")" # Will be removed in release.
---
>     then IGNITE_HOME_TMP="$(dirname "$(cd "$(dirname "$0")"; "pwd")")";
114c114
<          -DIGNITE_HOME="${IGNITE_HOME}" -DIGNITE_PROG_NAME="$0" \
---
>         -DIGNITE_UPDATE_NOTIFIER=false -DIGNITE_HOME="${IGNITE_HOME}" -DIGNITE_PROG_NAME="$0"
\
119c119
<         "$JAVA" ${JVM_OPTS} ${QUIET}  \
---
>         "$JAVA" ${JVM_OPTS} ${QUIET} -DIGNITE_UPDATE_NOTIFIER=false \


It looks like line 26 is wrong. Please, fix it.


was (Author: vsidorova):
Ubuntu 14.04, Ignate Fabric Only Build #114 for ignite-185 branch (ver. 1.0.0-RC2-SNAPSHOT#20150304-sha1:e9356ab0):
--------------------------------------------------------
Now ./ignitevisorcmd.sh doesn't start yet with next errors:

isla@isla:~/Ignite/sp2/ignite-fabric-1.0.0-RC2-SNAPSHOT/bin$ ./ignitevisorcmd.sh 
./ignitevisorcmd.sh: line 35: /home/isla/Ignite/sp2/bin/include/functions.sh: No such file
or directory
./ignitevisorcmd.sh: line 40: checkJava: command not found
./ignitevisorcmd.sh: line 45: setIgniteHome: command not found
./ignitevisorcmd.sh: line 50: /home/isla/Ignite/sp2/bin/include/parseargs.sh: No such file
or directory
./ignitevisorcmd.sh: line 55: /home/isla/Ignite/sp2/bin/include/setenv.sh: No such file or
directory
./ignitevisorcmd.sh: line 119: : command not found
isla@isla:~/Ignite/sp2/ignite-fabric-1.0.0-RC2-SNAPSHOT/bin$ 

--------------------------------------------------------
The results of diff command between new and old script is:

26c26
<     then IGNITE_HOME_TMP="$(dirname "$(cd "$(dirname "$0")"; "pwd")")";IGNITE_HOME_TMP="$(dirname
"${IGNITE_HOME_TMP}")" # Will be removed in release.
---
>     then IGNITE_HOME_TMP="$(dirname "$(cd "$(dirname "$0")"; "pwd")")";
114c114
<          -DIGNITE_HOME="${IGNITE_HOME}" -DIGNITE_PROG_NAME="$0" \
---
>         -DIGNITE_UPDATE_NOTIFIER=false -DIGNITE_HOME="${IGNITE_HOME}" -DIGNITE_PROG_NAME="$0"
\
119c119
<         "$JAVA" ${JVM_OPTS} ${QUIET}  \
---
>         "$JAVA" ${JVM_OPTS} ${QUIET} -DIGNITE_UPDATE_NOTIFIER=false \


It looks like line 26 is wrong. Please, fix it.

> 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
>
>
> 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