Comments
To make sure it's not a test report format issue, I also tested the following configuration: It works, I got test statistics on job details page.Thanks, I'm looking forward it.
Will there be some video recorded for this webinar?
Ok, you confirmed that the GUID of Cruise Agent changed. The way Cruise Server references an agent is with its GUID. If it changed, Cruise Server will treat the old one as "lost contact", and the new one as "pending".
We noticed before that sometimes antivirus software affectes Cruise Agent on accessing config\guid.txt. So for your case I would first suggest you to stop Trend Micro OfficeScan for sometime and see if the issue is still there. If that's the cause you can either stop it (if it's ok) or exclude scaning of the Cruise Agent\config folder.
Hi Jason, from your description it seems not the IP address issue. Each Cruise agent has its own GUID and won't require approval again once approved, unless the GUID changed.
So can you check if the agent GUID changed after restarting that machine? You can check the content of [Agent_Installation_path]/config/guid.txt to verify it.
If the answer is yes, then do you have antivirus/firewall software installed on the agent machine? And please tell us the version of Cruise you're using.
Hi kishore, it's very nice to hear that you're interested in this. You don't need to install subversion on the TFS server, but you do need it on the Cruise server and agent.
Hi, you missed the database name. The correct URL should be as following:
jdbc:h2:[location-of-your-db-folder]/cruise
Also, Cruise provides Restful API to get information around your build. You can take a look at this to see how to use it.
You can take a look at the browser url when the 404 error happens, see if it's http://localhost or http://ip_address...
There is a limitation in IE that accessing localhost can not use proxy. If that's the case you need to make sure your twist tests use http://ip_address/... as your browser url instead of http://localhost/...
Hi GJ, I was on holiday last week, sorry for the delayed reply.
The error message you found in cruise-server.log answered all the confusion. It's not the certificate stuff at all, it's because Cruise can not find the program "svn".
Usually this means there is svn.bat or svn.cmd in your system path, not svn.exe.
What's svn client in your system? Cruise doesn't support tortoise svn.
Then, can the Cruise server access svn https server? If not, take a look at the Log On of the Cruise Server service, make sure the Log On user is the correct one that has saved svn server certificate.
windows_services_owner.jpg (33KB)Hi GJ, I don't understand your problem, my question is:
What do you mean for "server and agent are running as svn user"?
In terms of "running as" I assume it means the windows user. Then you need to make sure logged in as this user you can access your svn repository correctly.
Hi Ade, yes you can allow Cruise stage to complete by killing the JBoss process. But with Ant there is better way for doing this: use the parallel daemon tasks. For example:
<parallel>
<daemon>
<exec ... //start JBoss server, don't turn on spawn
</daemon>
<junit ... //run your tests
</parallel>When Ant exists it will kill daemon processes.
For the second question, you got the right way, but a little different. It depends on the error code returned from your bat(ci\package-and-test.bat) not ANT, 0 for success or non-zero for failure.
Hi Juan, supporting use your SCM revision in pipeline label template is in our backlog.
Cruise1.2 renamed the <dependencies> element to pipeline dependency and provide fetch artifact support. So if pipeline A depends on pipeline B, when pipeline A build, you can use <fetchartifact> to get the version of pipeline B that triggered pipeline A.
You can download Cruise1.2 and try it out.
Also not sure why do you want to build pipeline B before building pipeline A. If the purpose is to use the latest version of pipeline B, the pipeline dependency should work, because everytime pipeline B is triggered, it will trigger pipeline A after it passed. Newer build of pipeline A are using newer version of pipeline B.
Hi Juan, your P4 view configuration is wrong, you missed the right part of your view mapping. For your case, it should be:
<p4 port="server:1666" username="cruise" password="cruisepassword">
<view><![CDATA[//depot/... //localclient/...]]></view>
</p4>
Take a look here for details, and a post as well.