Test results in shell project
Hi, I would like to include the building and testing of a Python project into Continuum. I can build the project fine as a Shell project, but is there any way to have Continuum recognize the test results? Is it enough to write out a jUnit-style XML file in the build directory somewhere that Continuum can pick up, or is there more too it? Thanks, Wim. -- ir. Wim Heirman, ELIS Department, Ghent University, Belgium Phone: +32-9-264.95.27 E-mail: [EMAIL PROTECTED] http://www.elis.UGent.be/~wheirman/
Re: Continuum report incorrect build results?
If you use maven 2.0.7, you must patch mvn.bat. It is explains in continuum FAQs Emmanuel On Thu, Feb 21, 2008 at 12:41 AM, Tawfik, Sameh E [EMAIL PROTECTED] wrote: When Continuum runs my maven 2 project, it send an email: [continuum] BUILD SUCCESSFUL:, but when I checked the build results I found out the build failed when it was building the last component, so why is Continuum is reporting success when the build failed? Does anyone know how to make Continuum detect this failure and correctly report back this result? The following is the build failed error messages: [javac] 33. ERROR in C:\Auto_Builds\working-directory\12\ csvimport\job\DelimImportJob.java (at line 128) [javac] ls.setCharacterSet(DelimitedLayoutImpl.CHARACTER_SET_EBCIDIC); [javac] ^ [javac] DelimitedLayoutImpl.CHARACTER_SET_EBCIDIC cannot be resolved BUILD FAILED C:\Auto_Builds\working-directory\12\mabc\build.xml:32: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:16: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:291: The following error occurred while executing this line: C:\Auto_Builds\working-directory\12\mabc\build.xml:258: Compile failed; see the compiler error output for details. Total time: 13 seconds [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing command line. Exit code:13 [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 25 minutes 14 seconds [INFO] Finished at: Wed Feb 20 15:23:17 PST 2008 [INFO] Final Memory: 23M/63M [INFO] This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.
Re: Windows path length limitation
its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED]
Re: How to apply a patch
if you have it in patch format then you would use the patch command something like patch -p0 issue.patch jesse On Tue, Feb 19, 2008 at 1:27 PM, Rafael da Silva Chiarinelli [EMAIL PROTECTED] wrote: Hi everyone, how can I apply a given patch in order to fix a bug? Best Regards, Rafael -- jesse mcconnell [EMAIL PROTECTED]
RE: Windows path length limitation
I agree its a limitation of the file system; however, if Continuum would feed Subversion an absolute path (when running svn commands) as opposed to a relative path then their would not be a 256 character limit. I tried this and it does work when I send Subversion an absolute path and it fails when I send it a relative path. I found an article about it online here: http://svn.haxx.se/users/archive-2005-02/1088.shtml. This shouldn't be a hard change to make and would allow Windows users to not have to worry about running into this problem. Kurt Date: Thu, 21 Feb 2008 10:48:08 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED]
Re: How to apply a patch
Jesse McConnell wrote: if you have it in patch format then you would use the patch command something like patch -p0 issue.patch jesse On Tue, Feb 19, 2008 at 1:27 PM, Rafael da Silva Chiarinelli [EMAIL PROTECTED] wrote: Hi everyone, how can I apply a given patch in order to fix a bug? Best Regards, Rafael hmmm, tks a lot! Rafael
RE: Windows path length limitation
I went ahead and logged an improvement to Maven SCM (http://jira.codehaus.org/browse/SCM-368). Hopefully they will fix this so Windows users won't have to experience this shortcoming. Kurt Date: Thu, 21 Feb 2008 11:22:36 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation oh interesting...You should check and see if there is an issue on this under maven SCM and if not open an issue there with this information http://jira.codehaus.org/browse/SCM jesse On Thu, Feb 21, 2008 at 11:15 AM, KURT TOMETICH [EMAIL PROTECTED] wrote: I agree its a limitation of the file system; however, if Continuum would feed Subversion an absolute path (when running svn commands) as opposed to a relative path then their would not be a 256 character limit. I tried this and it does work when I send Subversion an absolute path and it fails when I send it a relative path. I found an article about it online here: http://svn.haxx.se/users/archive-2005-02/1088.shtml. This shouldn't be a hard change to make and would allow Windows users to not have to worry about running into this problem. Kurt Date: Thu, 21 Feb 2008 10:48:08 -0600 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation its a limitation of the file system...not a lot we can do about it :( On Tue, Feb 19, 2008 at 12:33 PM, KURT TOMETICH [EMAIL PROTECTED] wrote: Thanks for the quick response. That was my fall-back option, but I wasn't sure if there was just an easy way to configure it to use an absolute path. Shortening the root path length should help, but its still possible to reach the limit. Kurt Date: Tue, 19 Feb 2008 18:19:23 +0100 From: [EMAIL PROTECTED] To: continuum-users@maven.apache.org Subject: Re: Windows path length limitation Try to configure Build Output Directory and Working Directory to c:\\bd and c:\\wd Go to the configuration entry of the administration menu [1] -- Olivier [1] http://maven.apache.org/continuum/docs/1.1/administrator_guides/configuration.html 2008/2/19, KURT TOMETICH [EMAIL PROTECTED]: Is there a way to configure Continuum to checkout project from Subversion using an absolute path instead of a relative path? This would solve the path limitation issue on Windows. I ran into the problem where the path was too long and was able to verify that if I checked out the project using an absolute path it worked fine. Is this something I can configure on and end user system or does the project have to be recompiled to make this change? Kurt -- jesse mcconnell [EMAIL PROTECTED] -- jesse mcconnell [EMAIL PROTECTED]
