Re: Problem in 1.1-beta-4

[Emmanuel Venisse]

Christian Edward Gruber a écrit :
Hmm.  further to this, it works on my Mac, and doesn't on my OpenBSD 
box, running jdk 1.5.0.  Before I had some problems with hte database 
not being created, which turned out to be related simply to available 
file descriptors.  At this point, I have pushed every ulimit category to 
its maximum, and I get no actual errors or problems that wuould indicate 
why it's not accepting the login.


I tried more ways, and explicitly tried bad passwords and bad usernames 
to ensure that it does, indeed, fail in more obvious ways in those 
cases.  It does.  In this case, it take it, accepts the password, but 
fails to set soemthing somewhere that is necessary for it to determine 
that the user IS logged in.  Maybe it's not creating a session 
properly?  I'm not sure.


Can I run continuum such that I get the debug output?  I'm sure I can, 
but I'm not sure what files to edit to do so.  Maybe something's showing 
in the logs.  Btu there are no ERROR logs showing at all.  Very 
frustrating.  It's probably configuration of the user, but I can't see 
what, since I've maxed it all out.


You can modify log levels in 
$CONTINUUM_HOME/apps/continuum/webapp/WEB-INF/classes/log4j.xml

Emmanuel


Christian.

On 30-Oct-07, at 4:29 PM, Christian Edward Gruber wrote:


Hi,

  I've unzipped beta4, run it, and it asks to create the admin user.  
I do that, and it goes to what seems like it should be system 
configuration, but it requires login.  I then attempt to login as 
admin (which was just created) and for a minute it looks like it was 
about to succeed, but then returns to the login screen.  This is 
distinct from a bad username/password, which show an error.  this just 
goes there like if you go to any url and you haven't been 
authenticated.  No matter what, whether I login or go elsewhere it 
just sends me back to the login page.


The log doesn't say much - just:

2007-10-30 11:37:45,428 [SocketListener0-0] INFO  
com.opensymphony.xwork.Action:redback-admin-account  - user = 
UserCredentials[username=admin,fullName=Build 
User,[EMAIL PROTECTED],password=<***>,confirmPassword=<***>] 

2007-10-30 11:37:46,123 [SocketListener0-0] INFO  
com.opensymphony.xwork.interceptor.Interceptor:redbackForceAdminUserInterceptor  
- Admin user found. No need to configure admin user.
2007-10-30 11:37:47,172 [SocketListener0-0] INFO  
com.opensymphony.xwork.Action:configuration  - 
baseUrl='http://207.188.87.165:8080/continuum'
2007-10-30 11:38:17,102 [SocketListener0-0] INFO  
com.opensymphony.xwork.Action:configuration  - 
baseUrl='http://207.188.87.165:8080/continuum'



These last two are the results of logging in as admin in the 
subsequently delivered login screens.


Any thoughts?

Christian.

Re: Multiple scheduled builds on the same project...

[Antonín Faltýnek]

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

Multiple scheduled builds on the same project...

[Eric D. Nielsen]

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

Re: Problem in 1.1-beta-4

[Christian Edward Gruber]

Hmm.  further to this, it works on my Mac, and doesn't on my OpenBSD  
box, running jdk 1.5.0.  Before I had some problems with hte database  
not being created, which turned out to be related simply to available  
file descriptors.  At this point, I have pushed every ulimit category  
to its maximum, and I get no actual errors or problems that wuould  
indicate why it's not accepting the login.


I tried more ways, and explicitly tried bad passwords and bad  
usernames to ensure that it does, indeed, fail in more obvious ways in  
those cases.  It does.  In this case, it take it, accepts the  
password, but fails to set soemthing somewhere that is necessary for  
it to determine that the user IS logged in.  Maybe it's not creating a  
session properly?  I'm not sure.


Can I run continuum such that I get the debug output?  I'm sure I can,  
but I'm not sure what files to edit to do so.  Maybe something's  
showing in the logs.  Btu there are no ERROR logs showing at all.   
Very frustrating.  It's probably configuration of the user, but I  
can't see what, since I've maxed it all out.


Christian.

On 30-Oct-07, at 4:29 PM, Christian Edward Gruber wrote:


Hi,

  I've unzipped beta4, run it, and it asks to create the admin  
user.  I do that, and it goes to what seems like it should be system  
configuration, but it requires login.  I then attempt to login as  
admin (which was just created) and for a minute it looks like it was  
about to succeed, but then returns to the login screen.  This is  
distinct from a bad username/password, which show an error.  this  
just goes there like if you go to any url and you haven't been  
authenticated.  No matter what, whether I login or go elsewhere it  
just sends me back to the login page.


The log doesn't say much - just:

2007-10-30 11:37:45,428 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:redback-admin-account  - user =  
UserCredentials[username=admin,fullName=Build User,[EMAIL PROTECTED] 
,password=<***>,confirmPassword=<***>]
2007-10-30 11:37:46,123 [SocketListener0-0] INFO   
com 
.opensymphony 
.xwork.interceptor.Interceptor:redbackForceAdminUserInterceptor  -  
Admin user found. No need to configure admin user.
2007-10-30 11:37:47,172 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:configuration  - baseUrl='http://207.188.87.165:8080/continuum'
2007-10-30 11:38:17,102 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:configuration  - baseUrl='http://207.188.87.165:8080/continuum'



These last two are the results of logging in as admin in the  
subsequently delivered login screens.


Any thoughts?

Christian.

Problem in 1.1-beta-4

[Christian Edward Gruber]

Hi,

   I've unzipped beta4, run it, and it asks to create the admin  
user.  I do that, and it goes to what seems like it should be system  
configuration, but it requires login.  I then attempt to login as  
admin (which was just created) and for a minute it looks like it was  
about to succeed, but then returns to the login screen.  This is  
distinct from a bad username/password, which show an error.  this just  
goes there like if you go to any url and you haven't been  
authenticated.  No matter what, whether I login or go elsewhere it  
just sends me back to the login page.


The log doesn't say much - just:

2007-10-30 11:37:45,428 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:redback-admin-account  - user =  
UserCredentials[username=admin,fullName=Build User,[EMAIL PROTECTED] 
,password=<***>,confirmPassword=<***>]
2007-10-30 11:37:46,123 [SocketListener0-0] INFO   
com 
.opensymphony 
.xwork.interceptor.Interceptor:redbackForceAdminUserInterceptor  -  
Admin user found. No need to configure admin user.
2007-10-30 11:37:47,172 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:configuration  - baseUrl='http://207.188.87.165:8080/continuum'
2007-10-30 11:38:17,102 [SocketListener0-0] INFO   
com.opensymphony.xwork.Action:configuration  - baseUrl='http://207.188.87.165:8080/continuum'



These last two are the results of logging in as admin in the  
subsequently delivered login screens.


Any thoughts?

Christian.

Re: [announce] Continuum 1.1-beta-4 is released

[Dennis Lundberg]

Emmanuel Venisse wrote:

The Continuum team is pleased to announce the Continuum 1.1-beta-4 release

Highlights are:

* lot of bug fixes
* A new page to view the build queue
* Customization of mail subject

You can grab the latest release from the download page : 
http://maven.apache.org/continuum/download.html


To upgrade from a previous 1.1 beta, you can look at Upgrade Guide : 
http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.html 


I followed the instructions above, but got an error message:

$ java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar 
-buildsJdbcUrl jdbc:derby:continuum-1.1-beta-3/data/continuum/database 
-mode EXPORT -file backups/builds


Invalid argument: -file

So I removed the file argument and got this:

$ java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar 
-buildsJdbcUrl jdbc:derby:continuum-1.1-beta-3/data/continuum/database 
-mode EXPORT


backups already exists and will not be overwritten unless the -overwrite 
flag is used.


I could not find any backup files in the backup directory, so I added 
the -overwrite flag


$ java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar 
-buildsJdbcUrl jdbc:derby:continuum-1.1-beta-3/data/continuum/database 
-mode EXPORT -overwrite


0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
Processing Continuum database...

...

and now the file 'backups/builds.xml' was created.


It was the same story for the users database. I had to use this command 
to get any new files in the backups directory:


$ java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar 
-usersJdbcUrl jdbc:derby:./continuum

-1.1-beta-3/data/users/database -mode EXPORT -overwrite

0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
Processing Redback database...

...




Below is the jira release notes for this release.

Release Notes - Continuum - Version 1.1-beta-4

Sub-task

* [CONTINUUM-1499] - Translate to Brazilian Portuguese
* [CONTINUUM-1534] - Translate to French

Bug

* [CONTINUUM-811] - Documentation of Deployment Repository Directory
* [CONTINUUM-1355] - No admin user found after Tomcat shutdown 
(Tomcat doesn't shutdown properly)

* [CONTINUUM-1392] - Continuum tests require too much external set up
* [CONTINUUM-1403] - Error on edit project group page
* [CONTINUUM-1453] - Confirmation Page for Deleting a Build 
Definition is not Informative Enough
* [CONTINUUM-1466] - Project name accepts blank spaces when edited 
in Project Summary > Members Tab > Edit Project
* [CONTINUUM-1473] - Server Id in wagon notifier edit pages is 
required but doesn't have validation
* [CONTINUUM-1474] - At the time of an addition of new 
BuildDefinition with XmlRPC client, the automatically generated 
buildDefinitionID cannot be recovered

* [CONTINUUM-1476] - warning/error in the mail generation
* [CONTINUUM-1481] - datamanagement-cli must support more db
* [CONTINUUM-1487] - should not be allowed to delete a build result 
that is still executing
* [CONTINUUM-1491] - Build history screen should show build 
definition description
* [CONTINUUM-1494] - Maximum length for name column exceeded in 
makeAndStoreBuildResult

* [CONTINUUM-1495] - Calling getAllProjectGroups() fails
* [CONTINUUM-1502] - After changing the name of a project group, the 
project dissapears and is not accessible, not even by the admin user.
* [CONTINUUM-1508] - NullPointerException when adding an empty 
installation to a profile
* [CONTINUUM-1509] - always build option doesn't work with scheduler 
--> log = No files updated, not building
* [CONTINUUM-1512] - Constraint Violation Exception when deleting an 
empty group
* [CONTINUUM-1516] - Unable to send mail with more than one build 
definition

* [CONTINUUM-1517] - missing includeBuildResult configuration
* [CONTINUUM-1519] - Continuum does not respect build order for flat 
projects

* [CONTINUUM-1520] - Scheduler is unstable
* [CONTINUUM-1524] - Continuum don't find the default build 
definition for ANT/Shell projects
* [CONTINUUM-1527] - NullPointer when Releasing without 
configuration node in the maven-release-plugin
* [CONTINUUM-1530] - Problems releasing project in group with more 
than one project definition
* [CONTINUUM-1532] - Remove TestResult/SuiteResult/TestCaseFailure 
from the model


Improvement

* [CONTINUUM-150] - Continuum site needs screenshots
* [CONTINUUM-606] - Add Build Time to Project Summary Page
* [CONTINUUM-703] - Display of last build date on Project Summary page
* [CONTINUUM-789] - Show SCM branch/tag on summary screen
* [CONTINUUM-815] - directory configuration
* [CONTINUUM-1233] - Reduce number of clicks to add a project
* [CONTINUUM-1254] - Clarification of Configuring Continuum as a 
Service in "Getting Started" Guide
* [CONTINUUM-1388] - the NOTICE file is overzealous in declaring 
dependenci

Re: Dealing with build variables

[Wendy Smoak]

On 10/30/07, Eric D Nielsen <[EMAIL PROTECTED]> wrote:

> I know its off-topic here, but it seems like an appropriate followup...  Is
> there a best practice for distributing setting.xml "templates" so that
> developers know what settings they need to configure before trying to build?

In a corporate (or otherwise "internal") environment, it's common to
customize the Maven distribution by replacing the settings.xml, and
have all your developers use the one you provide.

-- 
Wendy

Export procedure hanging

[Graham Leggett]

Hi all,

Following the export procedure at
http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.html,
the export seems to hang at this point:

bash-3.00$ java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar
-buildsJdbcUrl
jdbc:derby:/udd001/app/alchemy/continuum/continuum-1.1-beta-3/data/continuum/database
-mode EXPORT -overwrite -directory continuum-1.1-beta-3/backups
0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  -
Processing Continuum database...

I double checked to ensure that continuum wasn't running at the time, but
it wasn't.

Are there any reasons why this should hang?

Regards,
Graham
--

Re: Dealing with build variables

[Eric D Nielsen]

On 10/28/07, Wendy wrote:
>On 10/28/07, Eric D Nielsen <[EMAIL PROTECTED]> wrote:
>
>> I have some integration tests that I want to run as part of the build
>> verification process.  These tests have to hit a database.  I've been using
>> Maven 2 based filtering to inject some properties into the appropriate
places.
>> But, of course, I don't want to check the database username/password into my
>> SCM.
>
>With Maven, "developer-specific" settings typically go in
>settings.xml.  Would adding some properties to the settings.xml file
>of the user who is running Continuum work for you?

Thank you.  Yes, that was the piece I was missing.  I've gotten my current setup
to work quite smoothly now.

I know its off-topic here, but it seems like an appropriate followup...  Is
there a best practice for distributing setting.xml "templates" so that
developers know what settings they need to configure before trying to build?

Eric

Re: Launch a trigger after each build of Continuum

[Emmanuel Venisse]

It isn't possible for the moment.

What type of script do you want to run?

Emmanuel

Martin Alejandro Villalobos a écrit :

Hello.
I want to run a shell script after each build of Continuum.
Some body know if there is some way for do it?

Thanks.

Martin.

Launch a trigger after each build of Continuum

[Martin Alejandro Villalobos]

Hello.
I want to run a shell script after each build of Continuum.
Some body know if there is some way for do it?

Thanks.

Martin.

Re: Out of Mem Problem with 1.1-beta 3

[Mac-Systems]

I solved my Problem:
In wrapper.conf you can set wrapper.java.maxmemory

regards,
Jens


Hello,

after around 100 Build suddenly Continuum throws an OOM Error.


I havent any special config made, the Error happens when i open the 
"Build Result".
Well the Result to display is quite big, anyway that should be normal 
for Tools like Continuum.


I'am using Maven 2.07 / Continuum 1.1-beta3.

java.lang.reflect.InvocationTargetException

Show/hide Stack Trace 
 



   java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 

at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:585)
at 
com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:358) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:218) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:192) 

at 
org.codehaus.plexus.xwork.interceptor.PlexusReleaseComponentInterceptor.intercept(PlexusReleaseComponentInterceptor.java:69) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175) 

at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) 

at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:72) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
org.codehaus.plexus.redback.xwork.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:118) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
org.codehaus.plexus.redback.xwork.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:178) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:58) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:175) 

at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) 

at 
com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.webwork.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:174) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.webwork.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:169) 

at 
com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) 

at 
com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) 

at 
co