[Anthill-pro] Error when running build second time

Monga, Sunita (GE Comm Fin) sunita.monga at ge.com
Mon Mar 31 11:26:37 CST 2008


Hi Steve,
 
I got the errror when I forced the build. I got the error in both cases
when there were changes and when there were no changes made since the
last build.
 
I also get the error when I have a scheduled trigger setup and there are
no changes since the last build, instead of getting a new build life is
not needed. The only difference is that the error shows up in the server
command window and not on the web UI.
 
The changelog step is configured to look at the start status of
"success".
 
Thanks

________________________________

From: anthill-pro-bounces at caladin.urbancode.com
[mailto:anthill-pro-bounces at caladin.urbancode.com] On Behalf Of Steve
Boone
Sent: Monday, March 31, 2008 11:27 AM
To: AnthillPro user and support list.
Cc: anthill-pro at caladin.urbancode.com
Subject: Re: [Anthill-pro] Error when running build second time


Sunita,

Did you try to force the build a second time, or is the problem that the
changelog is not picking up any changes?  How do you have your changelog
step configured?  Most likely you will want to get the changes from the
last "Success" status.  If you do not have a status selected for your
chagelog step, then it will not work. 

Were any changes made since you tried to do the build again?  If not,
and you did not force the build, it would tell you that a new build life
was not needed.  


On Fri, Mar 28, 2008 at 12:47 PM, Monga, Sunita (GE Comm Fin)
<sunita.monga at ge.com> wrote:



	Hi, 

	I am new to Anthill pro. I setup a simple workflow and job to
build the project using ant script. I was able to force the build the
first time and it completed fine. However any subsequent builds give
following errors in Get Changelog step:

	Errors: 
	 BuildLifeJobTrace Failed 2008-03-28 11:36:33,152 ERROR 387 -
Caught unexpected exception 
	 Step 2: Get Changelog Failed 2008-03-28 11:36:33,136 ERROR 387
1 - PostProcessingScript Failing command: ExitCode 1 was not in {0}

	   view output 
	cvs log: Logging ecommerce/serviceRunner/appl/lib 
	cvs log: Logging ecommerce/serviceRunner/appl/metadata 
	cvs log: Logging ecommerce/serviceRunner/build 
	CVS command exit status: 1 
	change-log-summary: com.urbancode.vcsdriver3.ChangeLogSummary { 
	  changeSetCount:      0 
	  changeCount:         0 
	  latestChangeSetUser: null 
	  latestChangeSetDate: 1969-12-31 18:00:00 -0600 


	2008-03-28 11:36:33,152 ERROR 387 - Caught unexpected exception 
	 com.urbancode.command.CommandResultException:
PostProcessingScript Failing command: ExitCode 1 was not in {0} 
	  at
com.urbancode.devilfish.services.command.CommandExecutionThread.postProc
essResult(CommandExecutionThread.java:175) 

	  at
com.urbancode.devilfish.services.command.CommandExecutionThread.run(Comm
andExecutionThread.java:119) 
	 2008-03-28 11:36:33,370 INFO 387 - Job 387 released working
directory C:\Program
Files\anthill3\agent\var\jobs\projects\serviceRunner\serviceRunner_workf
low on agent sunitaAgent 

	 2008-03-28 11:36:33,370 INFO 387 - Job Trace
com.urbancode.anthill3.domain.jobtrace.buildlife.BuildLifeJobTrace [387]
released acquired agent tcp://127.0.0.1:4568
(endpointId=c2Z4MzBrMnhxMzMxeW1vaTU0MD

	Thanks 

	Sunita 


	_______________________________________________
	Anthill-pro mailing list
	Anthill-pro at lists.urbancode.com
	http://lists.urbancode.com/mailman/listinfo/anthill-pro
	
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.urbancode.com/pipermail/anthill-pro/attachments/20080331/2593af64/attachment.htm


More information about the Anthill-pro mailing list