Continuum 1.1-beta-3 crashing while adding a new project group
Hi, I have been using Continuum 1.1-beta-3 since more than a month now and it has been running smoothly. But today I attempted to add some more project groups to it, and it crashed giving me a primary key constraint violation. Attached is the stacktrace. I did migrate my data from 1.1-beta3 from beta 2 before starting to use beta-3. Could that have caused the problem ? This is the 1st problem I have faced since the migration. All the other data migrated smoothly, and I have been able to add/edit schedules,projects, build definitions since then. Help will be appreciated. Regards, Anshula http://www.nabble.com/file/p13756617/Stacktrace.txt Stacktrace.txt -- View this message in context: http://www.nabble.com/Continuum-1.1-beta-3-crashing-while-adding-a-new-project-group-tf4808053.html#a13756617 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Continuum 1.1-beta-3 crashing while adding a new project group
Hi Oliver, Thanks for the reply. No I have not made any change to the SEQUENCE_TABLE. Should that cause this error ? Isnt there any other way to correct this error now? Coz I have already imported data from beta2 to beta3 long time back..And made quite a few updates after that... Regards, Anshula olivier lamy wrote: Hi, Have a look at http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.htmlsection Importing Data to the new version. Have you made the update in SEQUENCE_TABLE ? -- Olivier 2007/11/14, Anshula [EMAIL PROTECTED]: Hi, I have been using Continuum 1.1-beta-3 since more than a month now and it has been running smoothly. But today I attempted to add some more project groups to it, and it crashed giving me a primary key constraint violation. Attached is the stacktrace. I did migrate my data from 1.1-beta3 from beta 2 before starting to use beta-3. Could that have caused the problem ? This is the 1st problem I have faced since the migration. All the other data migrated smoothly, and I have been able to add/edit schedules,projects, build definitions since then. Help will be appreciated. Regards, Anshula http://www.nabble.com/file/p13756617/Stacktrace.txt Stacktrace.txt -- View this message in context: http://www.nabble.com/Continuum-1.1-beta-3-crashing-while-adding-a-new-project-group-tf4808053.html#a13756617 Sent from the Continuum - Users mailing list archive at Nabble.com. -- View this message in context: http://www.nabble.com/Continuum-1.1-beta-3-crashing-while-adding-a-new-project-group-tf4808053.html#a13757364 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: NullPointerException when adding a new build definition
Hi, Even I observed the same bug. After opening the build definition for each project and saving it again, the builds start working correctly. But today I observed another bug. I have an existing default build definition for each of my projects (that has been exported from Continuum-beta2) . I tried to add another build definition today in my latest Continuum beta3 version and it is giving me the following exception - org.apache.maven.continuum.ContinuumException: Error while executing the action 'add-build-definition-to-project-group'. And underneath this exception I get a NullPointerException. The whole Stacktrace is in the attached file. I observed the same behaviour for both Maven2 and Ant projects. Any help will be appreciated...Thanks, Anshula http://www.nabble.com/file/p13007750/Stacktrace.txt Stacktrace.txt olivier lamy wrote: Hi, Yes it is (an issue). If you have some updates to do on the derby database, you can stop continuum and use squirrel [1] -- Olivier [1]http://squirrel-sql.sourceforge.net/ 2007/10/2, Iker Almandoz [EMAIL PROTECTED]: Some more information that can be helpful: I have checked the project and no 'type' information is given for all the build definitions after the import was done... so this might be an issue with the import tool... To fix it, i went to the project view, Build definition and edited the default build definition to have type='maven2' Regards, Iker On 10/1/07, Iker Almandoz [EMAIL PROTECTED] wrote: Hi, I tried to add a new porject to my continuum-1.1-beta-3 and got a NullPointerException Then i've tried to execute the default target for this project from the project group view page and got a org.apache.maven.continuum.ContinuumException: Project (id=280 doens't have a default build definition. However, if i go to the actual project I do see a build definition, and if I click on it, the project builds successfully. Below is the log from the NullPointerException and the stacktrace i got when trying to add a build definition... Any ideas ? Please let me know if i can provide any more info to help debug this issue, Best regards, Iker INFO | jvm 1| 2007/10/01 18:46:43 | 2007-10-01 18:46:43,308 [pool-2-thread-1] INFO ContinuumScm:default - Checking out project: 'My Projet', id: '280' to '/usr/local/ continuum- 1.1-beta-3/apps/continuum/webapp/WEB-INF/working-directory/280'. INFO | jvm 1| 2007/10/01 18:46:43 | 2007-10-01 18:46:43,334 [pool-2-thread-1] INFO ScmManager:default - Executing: /bin/sh -c cd /usr/local/ continuum- 1.1-beta-3/apps/continuum/webapp/WEB-INF/working-directory cvs -f -d :ext:[EMAIL PROTECTED]:/cvs -q checkout -d 280 my_project INFO | jvm 1| 2007/10/01 18:46:43 | 2007-10-01 18:46:43,334 [pool-2-thread-1] INFO ScmManager:default - Working directory: /usr/local/continuum- 1.1-beta-3 /apps/continuum/webapp/WEB-INF/working-directory INFO | jvm 1| 2007/10/01 18:46:44 | 2007-10-01 18:46:44,096 [pool-2-thread-1] INFO ContinuumScm:default - Checked out 2 files. INFO | jvm 1| 2007/10/01 18:47:06 | 2007-10-01 18:47:06,773 [SocketListener0-0] INFO Continuum:default - exception INFO | jvm 1| 2007/10/01 18:47:06 | java.lang.NullPointerException INFO | jvm 1| 2007/10/01 18:47:06 | at org.jpox.state.StateManagerImpl.internalMakePersistent( StateManagerImpl.java:3667) INFO | jvm 1| 2007/10/01 18:47:06 | at org.jpox.state.StateManagerImpl.makePersistent (StateManagerImpl.java:3646) INFO | jvm 1| 2007/10/01 18:47:06 | at org.jpox.AbstractPersistenceManager.internalMakePersistent( AbstractPersistenceManager.java:1202) INFO | jvm 1| 2007/10/01 18:47:06 | at org.jpox.AbstractPersistenceManager.makePersistent( AbstractPersistenceManager.java:1261) INFO | jvm 1| 2007/10/01 18:47:06 | at org.codehaus.plexus.jdo.PlexusJdoUtils.updateObject (PlexusJdoUtils.java:160) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven.continuum.store.JdoContinuumStore.updateObject( JdoContinuumStore.java:855) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven.continuum.store.JdoContinuumStore.updateObject (JdoContinuumStore.java:847) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven. continuum.store.JdoContinuumStore.updateProject(JdoContinuumStore.java :1232) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven.continuum.core.action.AddBuildDefinitionToProjectAction.execute ( AddBuildDefinitionToProjectAction.java:51) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven.continuum.DefaultContinuum.executeAction (DefaultContinuum.java:2715) INFO | jvm 1| 2007/10/01 18:47:06 | at org.apache.maven.continuum.DefaultContinuum.addBuildDefinitionToProject
Re: [announce] Continuum 1.1-beta-3 is released
just upgraded my continuum-1.1-beta-2 installation to beta-3. The new version looks very good. I upgraded my continuum database for the 1st time, it worked as a charm using the data management utility. :) Great work..!! Regards, Anshula Jesse McConnell wrote: hm, probably not right now...I'll have to provide for that in the plexus ldap helper. I tested this against a setup where I had a utility user that I used for that initial bind operation and at the time wasn't able to get the apacheds unit testing working so the number of scenarios I could test against was limited. I'll definitely have to make a test for this though now that I have that ability again. If you like open a redback issue for this at http://jira.codehaus.org/browse/REDBACK to track progress on it. I am also going to put the configuration bits for ldap into the security.properties as well since its a bit bothersome to have to set those things up in the application.xml like it is currently. jesse On 9/26/07, Cla Emanuel Monsch [EMAIL PROTECTED] wrote: hi there, is it possible to use ldap without bindDN/password? (anonyous bind) with the config bellow i got the following error: configuration hostname/hostname port389/port baseDndc=netcetera,dc=ch/baseDn contextFactorycom.sun.jndi.ldap.LdapCtxFactory/contextFactory password/password bindDn/bindDn /configuration configuration email-attributedescription/email-attribute full-name-attributegecos/full-name-attribute password-attributeuserPassword/password-attribute user-id-attributeuid/user-id-attribute user-base-dndc=netcetera,dc=ch/user-base-dn user-object-classinetOrgPerson/user-object-class /configuration INFO | jvm 1| 2007/09/26 14:23:26 | 2007-09-26 14:23:26,127 [SocketListener0-1] WARN ConfigurationFactory - No configuration found. Configuring ehcache fr om ehcache-failsafe.xml found in the classpath: jar:file:/share/nca05/build/servers/arcturus/continuum-1.1-beta-3 /apps/continuum/webapp/WEB-INF/lib/ehcache-1.2.4.jar!/ehc ache-failsafe.xml INFO | jvm 1| 2007/09/26 14:23:30 | 2007-09-26 14:23:30,244 [SocketListener0-1] INFO LdapController:default - Searching for user: guest INFO | jvm 1| 2007/09/26 14:23:30 | 2007-09-26 14:23:30,245 [SocketListener0-1] INFO LdapController:default - Searching for users with filter: '((objectCla ss=inetOrgPerson)(uid=guest))' from base dn: dc=netcetera,dc=ch INFO | jvm 1| 2007/09/26 14:23:30 | 2007-09-26 14:23:30,265 [SocketListener0-1] ERROR DispatcherUtils- Could not find action INFO | jvm 1| 2007/09/26 14:23:30 | Caught Exception while registering Interceptor class redbackEnvironmentCheckInterceptor - Class: org.codehaus.plexus.redback.xwor k.checks.security.GuestUserEnvironmentCheck INFO | jvm 1| 2007/09/26 14:23:30 | File: GuestUserEnvironmentCheck.java INFO | jvm 1| 2007/09/26 14:23:30 | Method: validateEnvironment INFO | jvm 1| 2007/09/26 14:23:30 | Line: 100 - org/codehaus/plexus/redback/xwork/checks/security/GuestUserEnvironmentCheck.java:100:-1 INFO | jvm 1| 2007/09/26 14:23:30 | at org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor( PlexusObjectFactory.java:152) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.InterceptorBuilder.constructInterceptorReference (InterceptorBuilder.java:56) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.lookupInterceptorReference (XmlConfigurationProvider.jav a:701) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStack (XmlConfigurationProvider.java:568) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptorStacks (XmlConfigurationProvider.java:581 ) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadInterceptors (XmlConfigurationProvider.java:602) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addPackage (XmlConfigurationProvider.java:204) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile (XmlConfigurationProvider.java:675 ) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.loadConfigurationFile (XmlConfigurationProvider.java:678 ) INFO | jvm 1| 2007/09/26 14:23:30 | at com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init( XmlConfigurationProvider.java:91) INFO | jvm 1| 2007/09/26 14:23:30
Re: Scheduled Builds Timing out
I dont think so. When I installed Continuum, I followed the standard installation instructions. I havent changed the logging configurations anywhere. These logs are for 1 day only. Continuum is running as a service and I have scheduled a build at 7:30 pm. Usually what I observe is that the logs get written at 7:30 pm when Continuum starts to checkout source and build the files. I am attaching one more file from a previo http://www.nabble.com/file/p12522974/wrapper.20070829.log wrapper.20070829.log us day as well, which has logs of some forced builds as well. Thanks Anshula Emmanuel Venisse wrote: 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 generate a build result. The only place that it logged about the timeout was the Continuum log file/Wrapper.log. Should it have generated a build result ? Coz it did not get built at all... Thanks, Anshula Emmanuel Venisse wrote: In build result page, choose a build result with timeout ant take the build id, then go to the build-output-directory and send us the content of the build output you'll find in this directory. Emmanuel Anshula a écrit : Hi Emmanuel, The File is as attached. Thanks for the help. Anshula Emmanuel Venisse wrote: Can you send your logs? Anshula a écrit : Hi Emmanuel, Acutally right now I am just building, there are no unit tests added as of now. The build does not take more than 1-2 minutes, I tried building all projects locally and verified this. Regards, Anshula Emmanuel Venisse wrote: Maybe you have a test that hang out? Emmanuel Anshula a écrit : Hello all, I am using Continuum 1.1-beta-2 with Perforce to integrate all my projects in the build management system. I have been using it over a month or so, and have around 15 project groups/projects integrated into it. I have scheduled a build in the system which runs at 7:30 pm everyday. The build system has been running properly building when it detects changes at the scheduled time But since 2 days, everyday the builds are timing out. I have set a Maximum job execution time of 3600 secs. Each of the projects does not take more than 1 minute to build. Continuum queues all the projects and prints a warning in the log file like - Task [EMAIL PROTECTED] didn't complete within time, cancelling it. And shows all the projects in queued state only. I need to restart Continuum to build them again. Thanks for your time. Any help will be appreciated. Regards, Anshula http://www.nabble.com/file/p12500482/wrapper.20070901.log wrapper.20070901.log -- View this message in context: http://www.nabble.com/Scheduled-Builds-Timing-out-tf4384387.html#a12522974 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Scheduled Builds Timing out
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. I still have't been able to get it working..! Thanks, Anshula Emmanuel Venisse wrote: 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 generate a build result. The only place that it logged about the timeout was the Continuum log file/Wrapper.log. Should it have generated a build result ? Coz it did not get built at all... Thanks, Anshula Emmanuel Venisse wrote: In build result page, choose a build result with timeout ant take the build id, then go to the build-output-directory and send us the content of the build output you'll find in this directory. Emmanuel Anshula a écrit : Hi Emmanuel, The File is as attached. Thanks for the help. Anshula Emmanuel Venisse wrote: Can you send your logs? Anshula a écrit : Hi Emmanuel, Acutally right now I am just building, there are no unit tests added as of now. The build does not take more than 1-2 minutes, I tried building all projects locally and verified this. Regards, Anshula Emmanuel Venisse wrote: Maybe you have a test that hang out? Emmanuel Anshula a écrit : Hello all, I am using Continuum 1.1-beta-2 with Perforce to integrate all my projects in the build management system. I have been using it over a month or so, and have around 15 project groups/projects integrated into it. I have scheduled a build in the system which runs at 7:30 pm everyday. The build system has been running properly building when it detects changes at the scheduled time But since 2 days, everyday the builds are timing out. I have set a Maximum job execution time of 3600 secs. Each of the projects does not take more than 1 minute to build. Continuum queues all the projects and prints a warning in the log file like - Task [EMAIL PROTECTED] didn't complete within time, cancelling it. And shows all the projects in queued state only. I need to restart Continuum to build them again. Thanks for your time. Any help will be appreciated. Regards, Anshula http://www.nabble.com/file/p12500482/wrapper.20070901.log wrapper.20070901.log -- View this message in context: http://www.nabble.com/Scheduled-Builds-Timing-out-tf4384387.html#a12525374 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Scheduled Builds Timing out
No even that is not the case. I have only 1 build definition and that too at the group level. I do not have any project level definitions. Regards, Anshula Emmanuel Venisse wrote: if forced build works fine, scheduled build should work too because it's the same code that run both. The possible difference is if you have more than one build definition, the forced build use the default one. About logs, you must have the same log for scheduled and forced builds. I don't understand what's happen. Emmanuel Anshula a écrit : I dont think so. When I installed Continuum, I followed the standard installation instructions. I havent changed the logging configurations anywhere. These logs are for 1 day only. Continuum is running as a service and I have scheduled a build at 7:30 pm. Usually what I observe is that the logs get written at 7:30 pm when Continuum starts to checkout source and build the files. I am attaching one more file from a previo http://www.nabble.com/file/p12522974/wrapper.20070829.log wrapper.20070829.log us day as well, which has logs of some forced builds as well. Thanks Anshula Emmanuel Venisse wrote: 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 generate a build result. The only place that it logged about the timeout was the Continuum log file/Wrapper.log. Should it have generated a build result ? Coz it did not get built at all... Thanks, Anshula Emmanuel Venisse wrote: In build result page, choose a build result with timeout ant take the build id, then go to the build-output-directory and send us the content of the build output you'll find in this directory. Emmanuel Anshula a écrit : Hi Emmanuel, The File is as attached. Thanks for the help. Anshula Emmanuel Venisse wrote: Can you send your logs? Anshula a écrit : Hi Emmanuel, Acutally right now I am just building, there are no unit tests added as of now. The build does not take more than 1-2 minutes, I tried building all projects locally and verified this. Regards, Anshula Emmanuel Venisse wrote: Maybe you have a test that hang out? Emmanuel Anshula a écrit : Hello all, I am using Continuum 1.1-beta-2 with Perforce to integrate all my projects in the build management system. I have been using it over a month or so, and have around 15 project groups/projects integrated into it. I have scheduled a build in the system which runs at 7:30 pm everyday. The build system has been running properly building when it detects changes at the scheduled time But since 2 days, everyday the builds are timing out. I have set a Maximum job execution time of 3600 secs. Each of the projects does not take more than 1 minute to build. Continuum queues all the projects and prints a warning in the log file like - Task [EMAIL PROTECTED] didn't complete within time, cancelling it. And shows all the projects in queued state only. I need to restart Continuum to build them again. Thanks for your time. Any help will be appreciated. Regards, Anshula http://www.nabble.com/file/p12500482/wrapper.20070901.log wrapper.20070901.log -- View this message in context: http://www.nabble.com/Scheduled-Builds-Timing-out-tf4384387.html#a12530927 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Scheduled Builds Timing out
Hi Emmanuel, The File is as attached. Thanks for the help. Anshula Emmanuel Venisse wrote: Can you send your logs? Anshula a écrit : Hi Emmanuel, Acutally right now I am just building, there are no unit tests added as of now. The build does not take more than 1-2 minutes, I tried building all projects locally and verified this. Regards, Anshula Emmanuel Venisse wrote: Maybe you have a test that hang out? Emmanuel Anshula a écrit : Hello all, I am using Continuum 1.1-beta-2 with Perforce to integrate all my projects in the build management system. I have been using it over a month or so, and have around 15 project groups/projects integrated into it. I have scheduled a build in the system which runs at 7:30 pm everyday. The build system has been running properly building when it detects changes at the scheduled time But since 2 days, everyday the builds are timing out. I have set a Maximum job execution time of 3600 secs. Each of the projects does not take more than 1 minute to build. Continuum queues all the projects and prints a warning in the log file like - Task [EMAIL PROTECTED] didn't complete within time, cancelling it. And shows all the projects in queued state only. I need to restart Continuum to build them again. Thanks for your time. Any help will be appreciated. Regards, Anshula http://www.nabble.com/file/p12500482/wrapper.20070901.log wrapper.20070901.log -- View this message in context: http://www.nabble.com/Scheduled-Builds-Timing-out-tf4384387.html#a12500482 Sent from the Continuum - Users mailing list archive at Nabble.com.
Problems with Space in Perforce URL Path
Hi, Today I tried adding an Ant project to Continuum with the SCM URL as - scm:perforce:[EMAIL PROTECTED]:1966://Project-Development/project - support libraries I am not able to build this Ant project. In the logs the error message is - Provider message: Unable to sync. Are you logged in? I tried adding another Ant project which has no spaces in the perforce path, and it built fine. Does continuum fail to build a project with spaces in the perforce URL ?? Has anyone faced the same problem? Regards Anshula -- View this message in context: http://www.nabble.com/Problems-with-Space-in-Perforce-URL-Path-tf4232434.html#a12041473 Sent from the Continuum - Users mailing list archive at Nabble.com.
Continuum with nAnt or MSBuild
Hi, I have some .NET projects which need to be integrated in Continuum. Has any one worked with setting up the build system for .NET projects with nAnt or MSBuild as the build tool. Any idea which build tool works better with Continuum? Regards, Anshula -- View this message in context: http://www.nabble.com/Continuum-with-nAnt-or-MSBuild-tf4212795.html#a11984115 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Continuum file url to pom.xml
Try this - file:///C:/location_of_clearcase_view/project/pom.xml The file protocol always starts with file:/// And in the file path, the separator should be / Regards, Anshula Roosendaal, Maarten wrote: Hi, We are trying to add a Maven 2(.0.7) project to Continuum (1.0.3). The pom.xml is part of a clearcase view so we have to fill in the M2 POM Url. Unfortunatly whatever we try it does not work: * file://localhost/c:/location_of_clearcase_view/project/pom.xml * file://c:/location_of_clearcase_view/project/pom.xml * file://localhost/c:\location_of_clearcase_view\project\pom.xml and then some. We've also tried following the instructions on: http://maven.apache.org/continuum/faqs.html#can-i-use-file-protocol-in-add-project-view but the specified folder is not there. I added it and changed all the application.xml's but with no luck We keep getting the message:[ You must provide a valid url (http, https, ftp and file protocols are allowed) ] Is this a bug or are we doing something wrong? There is a clearcase view already present there. Thanks, Kind regards / Met vriendelijke groeten, Maarten Roosendaal / Capgemini / Netherlands Senior Consultant / Java Assembly Line / ADC Technologies T. +31 30 68 970 77 / Mob. +31 6 248 216 12 www.nl.capgemini.com Join the Collaborative Business Experience This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. -- View this message in context: http://www.nabble.com/Continuum-file-url-to-pom.xml-tf4110435.html#a11689819 Sent from the Continuum - Users mailing list archive at Nabble.com.
RE: Unable to sync from Perforce if Continuum is run as a service
I did try both ways - 1. using Local System account 2. by selecting the other option and changing the login to my account by supplying the user name and password so that the service runs under my account It gives the same error either ways. What do you mean by environment variable / right differences ? My environment variables look fine, i guess the only one it looks for is MAVEN_HOME and JAVA_HOME, which is set in the System variables in my case. Could it have something to do with perforce? Regards, Anshula John Coleman-6 wrote: If your Windows service runs under a different profile, then maybe there could be environment variables and rights differences? I have Continuum 1.0.3 running fine as a service using Local System Account. John Coleman, MSTA Senior Developer Consultant Eurobase Banking Solutions Bury House, 31 Bury Street, London EC3A 5AG, U.K. Office: +44 (0)1245 496 706, Fax: +44 (0)20 7626 6203 Mobile: +44 (0)7734 506586 -Original Message- From: Anshula [mailto:[EMAIL PROTECTED] Sent: 19 July 2007 14:51 To: continuum-users@maven.apache.org Subject: Unable to sync from Perforce if Continuum is run as a service Hi, I have been trying to setup a build system using continuum for our projects. I have a Maven2 project(with modules) and the SCM is Perforce. Initially, I started continuum from the command line using the batch file bin\windows-x86-32\run.bat. I was able to add the project successfully from the UI and build it as well. After that I tried to setup Continuum as a service using the script bin\windows-x86-32\InstallService.bat. Again I tried to build the same project again. But it refuses to build. Following is the part of error trace - --- INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,333 [pool-1-thread-1] INFO ScmManager:default - Executing: p4 -d C:\Try\project\254 -p hydrogen:1666 -u username client -i INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Error while checking out the code for project: 'project-trial', id: '254' to 'C:\Try\project\254'. INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Command output: INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Provider message: Unable to sync. Are you logged in? INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] INFO BuildController:default- Merging SCM results INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,412 [pool-1-thread-1] INFO BuildController:default- Error updating from SCM, not building --- The version of Continuum that I am using is continuum-1.1-alpha-2 and the maven version is 2.0.5. Also, here is the SCM Section of my parent POM (if needed) - --- scm connectionscm:perforce:[EMAIL PROTECTED]:1666://Java-Development/pro ject-trial/connection developerConnectionscm:perforce:[EMAIL PROTECTED]:1666://Java-Develo pment/project-trial/developerConnection /scm .. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0/version configuration connectionTypedeveloperConnection/connectionType usernameusername/username passwordpassword/password /configuration /plugin /plugins /build --- What possibly can be wrong? The same configration works fine while Continuum is in command line mode? Thanks, Anshula -- View this message in context: http://www.nabble.com/Unable-to-sync-from-Perforce-if-Continuum-is-run-a s-a-service-tf4111233.html#a11689772 Sent from the Continuum - Users mailing list archive at Nabble.com. Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments
Unable to sync from Perforce if Continuum is run as a service
Hi, I have been trying to setup a build system using continuum for our projects. I have a Maven2 project(with modules) and the SCM is Perforce. Initially, I started continuum from the command line using the batch file bin\windows-x86-32\run.bat. I was able to add the project successfully from the UI and build it as well. After that I tried to setup Continuum as a service using the script bin\windows-x86-32\InstallService.bat. Again I tried to build the same project again. But it refuses to build. Following is the part of error trace - --- INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,333 [pool-1-thread-1] INFO ScmManager:default - Executing: p4 -d C:\Try\project\254 -p hydrogen:1666 -u username client -i INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Error while checking out the code for project: 'project-trial', id: '254' to 'C:\Try\project\254'. INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Command output: INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] WARN ContinuumScm:default - Provider message: Unable to sync. Are you logged in? INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,396 [pool-1-thread-1] INFO BuildController:default- Merging SCM results INFO | jvm 1| 2007/07/18 16:00:00 | 2007-07-18 16:00:00,412 [pool-1-thread-1] INFO BuildController:default- Error updating from SCM, not building --- The version of Continuum that I am using is continuum-1.1-alpha-2 and the maven version is 2.0.5. Also, here is the SCM Section of my parent POM (if needed) - --- scm connectionscm:perforce:[EMAIL PROTECTED]:1666://Java-Development/project-trial/connection developerConnectionscm:perforce:[EMAIL PROTECTED]:1666://Java-Development/project-trial/developerConnection /scm .. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.0/version configuration connectionTypedeveloperConnection/connectionType usernameusername/username passwordpassword/password /configuration /plugin /plugins /build --- What possibly can be wrong? The same configration works fine while Continuum is in command line mode? Thanks, Anshula -- View this message in context: http://www.nabble.com/Unable-to-sync-from-Perforce-if-Continuum-is-run-as-a-service-tf4111233.html#a11689772 Sent from the Continuum - Users mailing list archive at Nabble.com.
