Hi,
I have the same problem. I want to run jboss after successful build
using exec ant task but this hangs continuum build. I believed that
adding spawn=true attribute will solve the problem (seems that ant
process waits for jboss process to finish, thus continuum waits too)
but result is the
Emmanuel Venisse wrote:
Which server do you want to restart?
jboss
but even I start simple bat file continuum is not finished until this
bat does not mark it's build as finished until this bat is not stopped
are you successful in restarting another server?
Maksimenko Alexander a écrit :
Emmanuel Venisse wrote:
Hmm, very strange.
Do you have updated your ant script?
http://maven.apache.org/continuum/faqs.html#how-does-continuum-detect-a-successful-build
yes of cause
has anybody tried to restart server in project build? I think it is
common task for continues integration
Which server do you want to restart?
Maksimenko Alexander a écrit :
Emmanuel Venisse wrote:
Hmm, very strange.
Do you have updated your ant script?
http://maven.apache.org/continuum/faqs.html#how-does-continuum-detect-a-successful-build
yes of cause
has anybody tried to restart server in
Emmanuel Venisse wrote:
Hmm, very strange.
Do you have updated your ant script?
http://maven.apache.org/continuum/faqs.html#how-does-continuum-detect-a-successful-build
yes of cause
has anybody tried to restart server in project build? I thought it is
common task for continues
Hmm, very strange.
Do you have updated your ant script?
http://maven.apache.org/continuum/faqs.html#how-does-continuum-detect-a-successful-build
Emmanuel
Maksimenko Alexander a écrit :
Emmanuel Venisse wrote:
BUILD SUCCESSFUL isn't a continuum message but a ant message.
it's perhaps a bug
Emmanuel Venisse wrote:
Can you send your continuum logs?
it's nothing odd in the log :
INFO Continuum - Enqueuing 'processbuilder' (Build
definition id=1).
INFO ContinuumScm - Updating project: id: '1', name
'processbuilder'.
INFO ScmManager
if it's all your logs, the ant process isn't finished because you should have
return code = 0 in log
Emmanuel
Maksimenko Alexander a écrit :
Emmanuel Venisse wrote:
Can you send your continuum logs?
it's nothing odd in the log :
INFO Continuum - Enqueuing
Emmanuel Venisse wrote:
if it's all your logs, the ant process isn't finished because you
should have return code = 0 in log
but if it's not finished - what does it mean BUILD SUCCESSFUL message
in continuum's log?
if I perform this task in shell then ant process will be finished
so may
BUILD SUCCESSFUL isn't a continuum message but a ant message.
it's perhaps a bug in ShellCommandHelper, the exit code is return by Process class and printed in
AbstractBuildExecutor (line 189).
so if you don't have Exit code: in your log, it's because Process objec
doesn't return it.
Can you
Emmanuel Venisse wrote:
BUILD SUCCESSFUL isn't a continuum message but a ant message.
it's perhaps a bug in ShellCommandHelper, the exit code is return by
Process class and printed in AbstractBuildExecutor (line 189).
so if you don't have Exit code: in your log, it's because Process
objec
hi!
I spent 2 days to the following problem :
I start executable in ant script
target name=
exec executable=cmd dir=. spawn=true
arg line=/C start calc.exe/
/exec
/target
the execution of ant script has been finished but continuum build is not
marked
hi!
I spent 2 days to the following problem :
I start executable in ant script
target name=
exec executable=cmd dir=. spawn=true
arg line=/C start calc.exe/
/exec
/target
the execution of ant script has been finished but continuum build is not
marked
Can you send your continuum logs?
Emmanuel
Maksimenko Alexander a écrit :
hi!
I spent 2 days to the following problem :
I start executable in ant script
target name=
exec executable=cmd dir=. spawn=true arg
line=/C start calc.exe/
/exec
/target
the
14 matches
Mail list logo
