Re: [c-1.1] Can't edit project notifiers?
On Dec 3, 2007 6:08 PM, Mick Knutson <[EMAIL PROTECTED]> wrote: > I have had to add an additional project notifier because the default one > does not allow me to edit it. How can I edit, or how does Continuum assign > the recipient to the default notifier? > > PROJECT NAME Type Recipient Events > Tools< > http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=61 > > > mail unknown Error/Failure/Success/Warning [image: Edit] [image: Delete] > Tools< > http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=61 > > > mail [EMAIL PROTECTED], latest committers > Error/Failure/Success/Warning [image: > Edit] > < > http://rc-sun66e.ut.dentegra.lab:8080/continuum/editProjectNotifier.action?projectId=61¬ifierType=mail&fromGroupPage=true&projectGroupId=6¬ifierId=408 > > > [image: > Delete] > < > http://rc-sun66e.ut.dentegra.lab:8080/continuum/deleteProjectNotifier.action?projectId=61&confirmed=false&fromGroupPage=true&projectGroupId=6¬ifierId=408 > > > WAR > Archetype< > http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=67 > > > mail unknown Error/Failure/Success/Warning [image: Edit] [image: Delete] > > I also added this to my master pom: > >continuum >http://rc-sun66e.ut.dentegra.lab:8080/continuum > > >mail >true >true >true >true >[EMAIL PROTECTED] > > > > > > > But that did not seem to help Or must I restart Continuum for that to > take affect? > > > > -- > Thanks, > Mick Knutson > > http://www.baselogic.com > http://www.blincmagazine.com > http://www.djmick.com > http://www.myspace.com/mickknutson > http://www.myspace.com/BLiNCMagazine > http://tahoe.baselogic.com > --- > There are two groups of notifiers, first that can be defined in project POM and could not be edited in Continuum, and second that can be defined in Continuum. That is probably the reason that you was not able to edit the notifier - it was defined in you POM. If make any changes into any POM, it is necessary to remove appropriate POM from maven repository used by Continuum. When Continuum updates project from SCM it will update all informations from project POM. Tonda Faltynek
Re: Multiple scheduled builds on the same project...
Dne středa 31. října 2007 Emmanuel Venisse napsal(a): > Antonín Faltýnek a écrit : > > Dne středa 31. října 2007 Eric D. Nielsen napsal(a): > >> I'm a little confused over how multiple build definitiions on different > >> schedules interact within a project. After reading several threads > >> it looks like my understand was correct, yet my installation doesn't > >> seem to behave as expected. > >> > >> I have three schedules set up: > >> Hourly > >> Every four hours > >> Nightly > >> > >> I have four build definitions > >> Hourly: clean test > >> Every four hours: clean integration-test > >> Nightly: clean install > >> Nightly: clean site site:deploy > >> > >> When a SVN commit occurs, the next hourly build shows that it detects > >> the > >> changes and builds. The nightly and four-hourly builds don't seem to > >> respond. > >> I thought that each schedule had its own "dirty" checker for SCM, so > >> that the fact > >> that their were no changes since the hourly build shouldn't stop > >> these other schedules > >> from running. However when I looked in the continuum working > >> directly, I see only a > >> single checked out project directory, so I wouldn't expect it to > >> think that the project > >> needs to be built > >> > >> So my questions are > >> > >> a) should the different builds function independently of each others > >> "updated-ness" > >> > >> b) if yes, where should I look to debug this? > >> c) if no, what's the correct configuration to establish my desired > >> build schedules? > >> > >> Thank you. > >> > >> Eric > > > > I had same issues Eric with version 1.0.3, then we upgraded to 1.1b3, > > which enables configuration, that specific build definition should be > > performed "ALWAYS", and that should be used "CVS CO" instead of "CVS > > UPDATE". > > With the latest 1.1 beta (1.1-beta-4), you don't need to run a clean build > with a checkout. All build definitions are independant and found all > changes from other builds since last execution even if the update return > nothing. Thats great. This will help very much. Many thanks to whole continuum team. > > > These two features can help you. > > > > Also there is issue, that if you have several build definitions (as in > > your example), then if your "nightly clean install" fail, but "nightly > > site site:deploy" performs successfully, you will se green "success" icon > > in project list and you have not good view on project state until you > > check build results. > > We'll try to find a solution for this in 1.2, but your 2 nightly builddef > "clean install" + "site site:deploy" can be rewrite with one builddef > "clean install site-deploy" Some times we had situation, that we need site even if, for example, fail any junit test. So we've divided these to execuions into separate build defs. Tonda
Re: Multiple scheduled builds on the same project...
Dne středa 31. října 2007 Eric D. Nielsen napsal(a): > I'm a little confused over how multiple build definitiions on different > schedules interact within a project. After reading several threads > it looks like my understand was correct, yet my installation doesn't > seem to behave as expected. > > I have three schedules set up: > Hourly > Every four hours > Nightly > > I have four build definitions > Hourly: clean test > Every four hours: clean integration-test > Nightly: clean install > Nightly: clean site site:deploy > > When a SVN commit occurs, the next hourly build shows that it detects > the > changes and builds. The nightly and four-hourly builds don't seem to > respond. > I thought that each schedule had its own "dirty" checker for SCM, so > that the fact > that their were no changes since the hourly build shouldn't stop > these other schedules > from running. However when I looked in the continuum working > directly, I see only a > single checked out project directory, so I wouldn't expect it to > think that the project > needs to be built > > So my questions are > > a) should the different builds function independently of each others > "updated-ness" > > b) if yes, where should I look to debug this? > c) if no, what's the correct configuration to establish my desired > build schedules? > > Thank you. > > Eric I had same issues Eric with version 1.0.3, then we upgraded to 1.1b3, which enables configuration, that specific build definition should be performed "ALWAYS", and that should be used "CVS CO" instead of "CVS UPDATE". These two features can help you. Also there is issue, that if you have several build definitions (as in your example), then if your "nightly clean install" fail, but "nightly site site:deploy" performs successfully, you will se green "success" icon in project list and you have not good view on project state until you check build results. Tonda
Re: Continuum under Tomcat & CVS
This is GREAT :-D whole my family will praise you as a hero ;) Using cvs_native solved all my problems and now continuum is fully functionall. When look back, there has to be some property configured in jetty or plexus that is not configured in tomcat. That is my only explanation of this issue. Thank you very much Emmanuel Best regards Tonda Dne čtvrtek 11. října 2007 Emmanuel Venisse napsal(a): > weird. standalone and webapp use the same cvs provider. > > If you prefer to use the native cvs instead of the java cvs, you can set > this property in your tomcat: > > -Dmaven.scm.provider.cvs.implementation=cvs_native > > Emmanuel > > Antonín Faltýnek a écrit : > > This is really funny, > > > > because I'm running on linux box, I'm not able to perform cvs login for > > 'ext' server and my repo is not run on pserver. > > > > So I tried connecting to cvs server through ssh using rsa key. > > > > When I configure (fresh install and upload of one POM) continuum, which > > was running as standalone, everything works fine. > > > > When I run continuum from Tomcat, under same user as before I got > > following error, I've same configuration, same user, only another > > container: > > > > 2007-10-11 15:53:19,506 [pool-1-thread-1] INFO > > BuildController:default- Initializing build > > 2007-10-11 15:53:19,513 [pool-1-thread-1] INFO > > BuildController:default- Starting build of TIF Utils > > 2007-10-11 15:53:19,552 [pool-1-thread-1] INFO > > BuildController:default- Purging exiting working copy > > 2007-10-11 15:53:19,552 [pool-1-thread-1] INFO > > BuildController:default- Performing action > > clean-working-directory 2007-10-11 15:53:19,554 [pool-1-thread-1] INFO > > BuildController:default- Updating working dir > > 2007-10-11 15:53:19,554 [pool-1-thread-1] INFO > > BuildController:default- Performing action > > check-working-directory 2007-10-11 15:53:19,557 [pool-1-thread-1] INFO > > BuildController:default- Performing action checkout-project > > 2007-10-11 15:53:19,560 [pool-1-thread-1] INFO > > ContinuumScm:default - Checking out project: 'TIF Utils', id: > > '6' to > > '/var/lib/tomcat-5.5/webapps/continuum/WEB-INF/working-directory/6'. > > 2007-10-11 15:53:19,561 [pool-1-thread-1] INFO > > ScmManager:default - > > Executing: /bin/sh -c "cd > > /var/lib/tomcat-5.5/webapps/continuum/WEB-INF/working-directory && cvs > > -z3 -f -d :ext:[EMAIL PROTECTED]:/cvs -q checkout -d 6 > > TIF_Utils" > > 2007-10-11 15:53:19,561 [pool-1-thread-1] INFO > > ScmManager:default - Working > > directory: > > /var/lib/tomcat-5.5/webapps/continuum/WEB-INF/working-directory > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,590 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - > > servletPath=/WEB-INF/jsp/projectView.jsp, pathInfo=null, > > queryString=null, name=null > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,590 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - Path Based Forward > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,592 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - > > servletPath=/WEB-INF/jsp/navigations/ProjectMenu.jsp, pathInfo=null, > > queryString=tab=view, name=null > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,592 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - Path Based Include > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,649 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - > > servletPath=/WEB-INF/jsp/components/buildDefinitionSummaryComponent.jsp, > > pathInfo=null, queryString=null, name=null > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,649 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - Path Based Include > > log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,687 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - Disabling the response for futher > > output log4j:ERROR Attempted to append to closed appender named [R]. > > 2007-10-11 15:53:19,688 [http-8080-Processor24] DEBUG > > ApplicationDispatcher - The Response is vehiculed using a > > wrapper: com.op
Re: Continuum under Tomcat & CVS
5.5/webapps/continuum/WEB-INF/working-directory/1'.
2007-10-10 08:36:05,043 [pool-1-thread-1] WARN
ContinuumScm:default - Command output:
2007-10-10 08:36:05,043 [pool-1-thread-1] WARN
ContinuumScm:default - Provider message: The cvs command failed.
2007-10-10 08:36:05,080 [pool-1-thread-1] INFO
BuildController:default- Merging SCM results
2007-10-10 08:36:05,192 [pool-1-thread-1] INFO
BuildController:default- Error updating from SCM, not building
Dne středa 26. září 2007 Emmanuel Venisse napsal(a):
> Do you have more informations about the SCM error in your build result?
>
> Emmanuel
>
> Antonín Faltýnek a écrit :
> > Dne středa 26. září 2007 Emmanuel Venisse napsal(a):
> >> For cvs (and continnum and maven) a user home is required because cvs
> >> store authentication in ${user.home}/.cvspass maven required it too to
> >> store the local repository and settings.xml
> >>
> >> Emmanuel
> >>
> >> Antonín Faltýnek a écrit :
> >>> Hi all,
> >>>
> >>> I have problem with Continuum 1.1 beta2, which I'm running on Linux box
> >>> under Tomcat 5.5. Continuum is not able to perform CVS update command,
> >>> when I use command from log file and run it as any other user it works
> >>> fine for me.
> >>>
> >>> Tomcat is running under user tomcat, which has no home directory
> >>> (/dev/null).
> >>>
> >>> Has anybody met (and happily solved :)) this issue?
> >>>
> >>> Thanks
> >>>
> >>> Tonda
> >
> > So I've created user home for tomcat, I haven't mentioned that for
> > connection I'm using ssh with rsa key, from command line it works fine,
> > tomcat is really running under tomcat user, but continuum still fails.
> >
> > (continuum is updating, because co was performed by hand)
> >
> > log snipped
> >
> > 38787 [http-8080-Processor25] DEBUG
> > org.apache.catalina.core.ApplicationDispatcher - Path Based Include
> > 38727 [pool-1-thread-1] INFO
> > org.apache.maven.continuum.scm.ContinuumScm:default - Updating project:
> > id: '1', name 'TIF Utils'.
> > 38980 [pool-1-thread-1] INFO
> > org.apache.maven.scm.manager.ScmManager:default -
> > Executing: /bin/bash -c "cd /var/lib/tomcat-5.5/webapps/continuum
> > /WEB-INF/working-directory/1 && cvs -z3 -f -q update -d"
> > 38980 [pool-1-thread-1] INFO
> > org.apache.maven.scm.manager.ScmManager:default - Working
> > directory: /var/lib/tomcat-5.5/webapps/continuum/WEB-INF/
> > working-directory/1
> > 39155 [http-8080-Processor25] DEBUG
> > org.apache.catalina.core.ApplicationDispatcher -
> > servletPath=/WEB-INF/jsp/components/companyLogo.jsp, pathInf
> > o=null, queryString=null, name=null
> > 39155 [http-8080-Processor25] DEBUG
> > org.apache.catalina.core.ApplicationDispatcher - Path Based Include
> > 40079 [pool-1-thread-1] WARN
> > org.apache.maven.continuum.scm.ContinuumScm:default - Error while
> > updating the code for project: 'TIF Utils', id: '
> > 1' to
> > '/var/lib/tomcat-5.5/webapps/continuum/WEB-INF/working-directory/1'.
> > 40080 [pool-1-thread-1] WARN
> > org.apache.maven.continuum.scm.ContinuumScm:default - Command output:
> > 40080 [pool-1-thread-1] WARN
> > org.apache.maven.continuum.scm.ContinuumScm:default - Provider message:
> > The cvs command failed.
> > 40123 [pool-1-thread-1] INFO
> > org.apache.maven.continuum.buildcontroller.BuildController:default -
> > Merging SCM results
> > 40622 [pool-1-thread-1] INFO
> > org.apache.maven.continuum.buildcontroller.BuildController:default -
> > Error updating from SCM, not building
Re: Continuum under Tomcat & CVS
Dne středa 26. září 2007 Emmanuel Venisse napsal(a):
> For cvs (and continnum and maven) a user home is required because cvs store
> authentication in ${user.home}/.cvspass maven required it too to store the
> local repository and settings.xml
>
> Emmanuel
>
> Antonín Faltýnek a écrit :
> > Hi all,
> >
> > I have problem with Continuum 1.1 beta2, which I'm running on Linux box
> > under Tomcat 5.5. Continuum is not able to perform CVS update command,
> > when I use command from log file and run it as any other user it works
> > fine for me.
> >
> > Tomcat is running under user tomcat, which has no home directory
> > (/dev/null).
> >
> > Has anybody met (and happily solved :)) this issue?
> >
> > Thanks
> >
> > Tonda
So I've created user home for tomcat, I haven't mentioned that for connection
I'm using ssh with rsa key, from command line it works fine, tomcat is really
running under tomcat user, but continuum still fails.
(continuum is updating, because co was performed by hand)
log snipped
38787 [http-8080-Processor25] DEBUG
org.apache.catalina.core.ApplicationDispatcher - Path Based Include
38727 [pool-1-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Updating project:
id: '1', name 'TIF Utils'.
38980 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default -
Executing: /bin/bash -c "cd /var/lib/tomcat-5.5/webapps/continuum
/WEB-INF/working-directory/1 && cvs -z3 -f -q update -d"
38980 [pool-1-thread-1] INFO
org.apache.maven.scm.manager.ScmManager:default - Working
directory: /var/lib/tomcat-5.5/webapps/continuum/WEB-INF/
working-directory/1
39155 [http-8080-Processor25] DEBUG
org.apache.catalina.core.ApplicationDispatcher -
servletPath=/WEB-INF/jsp/components/companyLogo.jsp, pathInf
o=null, queryString=null, name=null
39155 [http-8080-Processor25] DEBUG
org.apache.catalina.core.ApplicationDispatcher - Path Based Include
40079 [pool-1-thread-1] WARN
org.apache.maven.continuum.scm.ContinuumScm:default - Error while updating
the code for project: 'TIF Utils', id: '
1' to '/var/lib/tomcat-5.5/webapps/continuum/WEB-INF/working-directory/1'.
40080 [pool-1-thread-1] WARN
org.apache.maven.continuum.scm.ContinuumScm:default - Command output:
40080 [pool-1-thread-1] WARN
org.apache.maven.continuum.scm.ContinuumScm:default - Provider message: The
cvs command failed.
40123 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default - Merging
SCM results
40622 [pool-1-thread-1] INFO
org.apache.maven.continuum.buildcontroller.BuildController:default - Error
updating from SCM, not building
Continuum under Tomcat & CVS
Hi all, I have problem with Continuum 1.1 beta2, which I'm running on Linux box under Tomcat 5.5. Continuum is not able to perform CVS update command, when I use command from log file and run it as any other user it works fine for me. Tomcat is running under user tomcat, which has no home directory (/dev/null). Has anybody met (and happily solved :)) this issue? Thanks Tonda
