Thanks for ur replies. But these are not solution. We use local pom files
for adding a new project to the Continuum. But Continuum use just SCM tags
from the local pom file. After that uses pom.xml files from Subversion. I
want taht Continnum use local pom files while integration operation. How
Can you explain why you don't want to use pom.xml from scm? If you want to use
specific settings for your continuous integration, it would be better to use
profiles in your pom
Emmanuel
albateos a écrit :
Thanks for ur replies. But these are not solution. We use local pom files
for adding a
ok, I'll try to add the build output even if the timeout appears
Emmanuel
Anshula a écrit :
Emmanuel,
In the build-output-directory of each project as well as on the build result
page, the last build that I can find is the last successful build.
The Builds that have a timeout, did not
Do you have redefined log levels? I don't see lot of logs in the file you sent.
Anshula a écrit :
Emmanuel,
In the build-output-directory of each project as well as on the build result
page, the last build that I can find is the last successful build.
The Builds that have a timeout, did not
Sorry for Spamming around ..
export LC_ALL=en_US.utf8
worked for me.
best regards,
Jens
I also Tested :
export LC_ALL=us_US.uft8
export LANG=us_US.uft8
On shell i get this:
/locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to
Hi,
same Maschine as my 1.0.3 version is running and i get this Error
Message when initial Checkout
should start (fresh added Maven 2 Project).
Provider message: The svn command failed.
Command output:
---
svn:
I don't know, but I don't think.
imossible to analyse with messages in logs and seems to works fine with forced
build
Emmanuel
Anshula a écrit :
Emmanuel,
Could it be an issue of Continuum and Perforce? I can see that there are
many open bugs regarding using Perforce as an SCM in Continuum.
