date:20060615

Re: build is not finished if start executable

2006-06-15 Thread Emmanuel Venisse


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 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 try with a non gui app?


yes
the same result ;(


Emmanuel

Maksimenko Alexander a écrit :

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 be incorrect work in ShellCommandHelper ?

ps this log message is appear when I close calculator application


Emmanuel

Maksimenko Alexander a écrit :

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 - Executing: svn --username 
*** --password * --non-interactive update
INFO  ScmManager - Working directory: 
D:\tools\dev\java\jakarta\continuum\bin\win32\..\..\apps\continuum\working-directory\1 


DEBUG ScmManager - At revision 3172.
NFO  Action:update-project-from-working-directory - Updating 
project 'processbuilder' from checkout.
INFO  ShellCommandHelper - Executing: 
D:\tools\dev\java\jakarta\ant\bin\ant -f build.xml continium
INFO  ShellCommandHelper - Working directory: 
D:\tools\dev\java\jakarta\continuum\bin\win32\..\..\apps\continuum\working-directory\1 




my build target:

   target name=continium
   exec executable=cmd dir=${engine.dir} 
spawn=true  arg line=/C start calc.exe/

   /exec

   waitfor maxwait=30 maxwaitunit=second 
timeoutproperty=server.is.unavailable

 http url=http://localhost/
   /waitfor  echofinish/echo
   /target

build result:

Buildfile: build.xml

continium:
[echo] finish

BUILD SUCCESSFUL


Total time: 39 seconds


but state is Build In Progess ;(

Re: Continuum 1.0.3 build is not updating status or sending emails

2006-06-15 Thread Emmanuel Venisse


What is the type of project?

Emmanuel

Gautham Pamu a écrit :

Hi Everyone,

I am using continuum 1.0.3 version. It has completed building the projects
but it says it is still in progress and it is not sending the build report
email. Is this a known problem
with continuum 1.0.3, is there was fix for it.


Jun 15, 2006 2:17:30 AM
Started since : 7 h 9 min 22 sec [image: Building]
Resulthttp://reposado.tivlab.austin.ibm.com/continuum/servlet/continuum/target/ProjectBuild.vm?view=ProjectBuildbuildId=8id=2 



[INFO] 

[INFO] 


[INFO] BUILD SUCCESSFUL
[INFO] 


[INFO] Total time: 69 minutes 30 seconds
[INFO] Finished at: Thu Jun 15 03:27:07 CDT 2006
[INFO] Final Memory: 65M/432M
[INFO] 




-Gautham Pamu

How to set scm value in pom for Clearcase?

2006-06-15 Thread Michael Waluk

Hi,
I'm trying to use Continuum 1.0.3 with Clearcase. In my pom.xml I have
specified the location of my config spec like this:

scmconnectionscm:clearcase:\\Xpw-rebuild101\rebuild_delta_6.1_int.vws\config_spec/connection/scm

This looks like the example at http://maven.apache.org/scm/clearcase.html and
it is the dynamic config spec on the VOB server. I've also tried creating
a . But when Continuum tries to build it looks like it is trying to connect
to the very same machine I am running it on. Is that an indication that it
doesn't like the value I gave it in the pom.xml? Should it start with
file:///Xpw-rebuild101 or something like that in URL format (it's windows if
that matters)?

I see in the console that it is trying this:
cleartool mkview -snapshot -tag Michael.Waluk-xpw-mwaluk1-maven-13-vws
\\xpw-mwaluk1\viewstore\Michael.Waluk-xpw-mwaluk1-maven-13.vwsfile://xpw-mwaluk1/viewstore/Michael.Waluk-xpw-mwaluk1-maven-13.vwsC:\java_sw\continuum-
1.0.3\apps\continuum\working-di
rectory\13

I tried giving another location as the view-name like this too:
scmconnectionscm:clearcase:*rebuild_delta_6.1_int.vws:*
\\Xpw-rebuild101\rebuild_delta_6.1_int.vws\config_spec/connection/scm
but it had no effect.

I have also tried placing a clearcase-settings.xml file in my home
directory's .scm directory. It contains this:

clearcase-settings
viewstore\\xpw-rebuild101\viewstore/viewstore
/clearcase-settings

I figured this might force Continuum to work there, but it didn't make a
difference. I get the error below no matter what I put in the pom it
seems. I would love to use Continuum with Clearcase (we use UCM VOBs) but
maybe it isn't fully implemented for Clearcase yet? Any help will be
greatly appreciated.

Thanks!
- Michael

Build Error:

Provider message: The cleartool command failed.

Command output:

---

albd_contact call failed: RPC: Unable to receive; errno = [WINSOCK]
Connection reset by peer

cleartool: Error: Unable to contact albd_server on host 'xpw-mwaluk1'

cleartool: Error: Cannot bind an admin_server handle on xpw-mwaluk1:
ClearCase object not found.

cleartool: Error: Unable to create view *
\\xpw-mwaluk1\viewstore\Michael.Waluk-xpw-mwaluk1-maven-1.vws*file://xpw-mwaluk1/viewstore/Michael.Waluk-xpw-mwaluk1-maven-1.vws
.

85 matches

Mail list logo