Chris Harris created CONTINUUM-2707:
---------------------------------------

             Summary: Real-time dashboard like Jenkins
                 Key: CONTINUUM-2707
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2707
             Project: Continuum
          Issue Type: Wish
          Components: Web interface
    Affects Versions: 1.4.1
            Reporter: Chris Harris
            Priority: Minor


Can you add a Dashboard to Continuum that would display icons for a build's state (red for
fail, green/blue for pass, yellow for warning),blinking icons (indicating that a build is
in progress), and a progress bar much like the Jenkins interface?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Murali Mohan created CONTINUUM-2706:
---------------------------------------

             Summary: Should we stop from queueing projects if another bulid is being executed?
                 Key: CONTINUUM-2706
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2706
             Project: Continuum
          Issue Type: Wish
    Affects Versions: 1.4.1
         Environment: Ubuntu, tomcat
            Reporter: Murali Mohan
            Priority: Minor


Problem and the argument
========================

It is difficult to balance the schedules when there are multiple projects running in Continuum.


One reason is that we cannot queue up builds from the same project is one is already being
executed. This is not needed in my opinion. The reason for having a queue is to avoid these
things. Let the build be queues and let it execut after the current one is done. What is wrong
with it?

Because of this restriction, we have to sometimes plan the schedule so that it executes only
after the any other projects having completed execution. This is a pain as we cannot predict
when a build will complete simply because we cannot know when it will start to execute as
there is a queue and there can be many builds in front.

Java code:
==========
CreateBuildProjectTaskAction.java:

This is the snippet where this occurs:

if ( executor.isBuilding( project ) || project.getState() == ContinuumProjectState.UPDATING
)
{
    // project is building
    getLogger().info( "Project '" + project.getName() + "' already being built." );

    continue;
}

Question
=========

Can we change it to this (we will continue with build process even if another one is being
executed):

if ( project.getState() == ContinuumProjectState.UPDATING )
{
    // project is building
    getLogger().info( "Project '" + project.getName() + "' already being built." );

    continue;
}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322225#comment-322225
] 

Murali Mohan commented on CONTINUUM-2705:
-----------------------------------------

ah yes, Brett, I had seen the change in r1140475, but I thought was a change done long back
and shouldn't have been highlighted now :). Anyways, patch submitted. No unit test that can
be done for this, but I have tested using the UI. The shell build runs fine, no more NPEs.
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: CONTINUUM-2705.patch, Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Murali Mohan updated CONTINUUM-2705:
------------------------------------

    Attachment: CONTINUUM-2705.patch

Patch for this case. This null check will only be done for Maven 1 and Maven 2 builds. Used
the ContinuumBuildExecutorConstants to match the build type stored in BuildDefinition.getType().

Would have been easier if BuildDefinition.getType was an Enum instead of a String.
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: CONTINUUM-2705.patch, Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322163#comment-322163
] 

Brett Porter commented on CONTINUUM-2705:
-----------------------------------------

The null check was introduced in r1140475 as part of CONTINUUM-2346. It seems it is just being
too aggressive. Perhaps it could be changed to only check for null on goals if it is a Maven
project. I dont see any reason why arguments needs to be non-null.
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322160#comment-322160
] 

Murali Mohan commented on CONTINUUM-2705:
-----------------------------------------

I did take a look. But I have not found anything obvious or anything that stands out so far.
I checked the SVN history to see if there was any changes in ParallelBuildsManager.java that
can impact.

But it looks like this section of code has existed for a long time. So why did it started
failing now, I am not able to figure out. Give me some pointers to proceed and I will try.
I have some time this week. Thanks
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322159#comment-322159
] 

Brett Porter commented on CONTINUUM-2705:
-----------------------------------------

Sorry to hear that. Do you have any time to look at what changed in that section of the code
that might have affected you?
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322157#comment-322157
] 

Brett Porter commented on CONTINUUM-2704:
-----------------------------------------

Thanks Murali, we should make sure this is applied to 1.4.2.
                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322158#comment-322158
] 

Murali Mohan commented on CONTINUUM-2705:
-----------------------------------------

It woks well in 1.3.6

Fails for the trunk version of code.
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2704:
------------------------------------

      Description: 
Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.

I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.

The problem is that, when the shell build from A runs, it will not execute the build until
the shell build from B is complete. it is almost  like A is waiting for B to finish. Please
note that maven builds are happily running in parallel in these 2 queues. It is only the shell
build that has a problem.

To be sure that this is not an OS level problem, I started the build in B from Continuum and
ran the shell script for A from command line and it worked fine - both ran in parallel. So,
I think Continuum has a bottle neck somewhere. please help.



  was:

Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.

I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.

The problem is that, when the shell build from A runs, it will not execute the build until
the shell build from B is complete. it is almost  like A is waiting for B to finish. Please
note that maven builds are happily running in parallel in these 2 queues. It is only the shell
build that has a problem.

To be sure that this is not an OS level problem, I started the build in B from Continuum and
ran the shell script for A from command line and it worked fine - both ran in parallel. So,
I think Continuum has a bottle neck somewhere. please help.



    Fix Version/s: 1.4.2
    
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322156#comment-322156
] 

Brett Porter edited comment on CONTINUUM-2705 at 3/19/13 10:35 AM:
-------------------------------------------------------------------

so, if I understand right, is this a regression over 1.3.6 for you? I assume it also fails
in 1.4.1.
                
      was (Author: brettporter):
    so, if I understand right, is this a regression over 1.3.6 for you?
                  
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2705:
------------------------------------

    Affects Version/s:     (was: 1.4.2)
                       1.4.1
        Fix Version/s: 1.4.2
    
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>             Fix For: 1.4.2
>
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322156#comment-322156
] 

Brett Porter commented on CONTINUUM-2705:
-----------------------------------------

so, if I understand right, is this a regression over 1.3.6 for you?
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=322129#comment-322129
] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

So I have made the change (removed the synchronize keyword) in the code I got for version
1.3.6 (from the corresponding branch). I couldn't get the trunk code to work which is explained
here - http://jira.codehaus.org/browse/CONTINUUM-2705

And this 1.3.6 version has been running and executing all our builds for more than a week
now. It is much faster and I am seeing less problems now. Initially, I used to have a load
of problems because of builds not getting completed on time as the shell builds were blocking
each other. Not any more.

So works well for me in 1.3.6


                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321661#comment-321661
] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

It is threadsafe, looks like that to me.

The only 2 variables I wanted to dig deep are defaultExecutable and resolveExecutable in AbstractBuildExecutor.
These variables are not set for ShellBuildExecutor where as it is being set ofrant and maven.
Any ideas why?

Anyways, I think we can safely make it a non-synchronized method.
                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2705?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321658#comment-321658
] 

Murali Mohan commented on CONTINUUM-2705:
-----------------------------------------

Information from Brett Porter:

"
It looks like it is validating based on Maven rules:

if ( buildDef.getArguments() == null || buildDef.getBuildFile() == null || buildDef.getGoals()
== null ||
 190                 buildDef.getSchedule() == null )

But I assume you don't need to provide goals for a shell task and that you might have that
empty.

- Brett
"
                
> Trunk 1.4.2-SNAPSHOT- error in Shell Build
> ------------------------------------------
>
>                 Key: CONTINUUM-2705
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.2
>         Environment: linux, tomcat
>            Reporter: Murali Mohan
>         Attachments: Screenshot-8.png
>
>
> I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).
> Screenshot of continuum UI showing the failing build (Test.sh) is also attached.
> Can someone please help? What is the reason for this error?
> StackTrace
> =========
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
> 2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
> org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due
to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> 2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
> org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action
'build-project'
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
>     at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
>     at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
>     at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
>     at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
>     at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
>     at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
>     at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
>     at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
>     ... 7 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Murali Mohan created CONTINUUM-2705:
---------------------------------------

             Summary: Trunk 1.4.2-SNAPSHOT- error in Shell Build
                 Key: CONTINUUM-2705
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2705
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.4.2
         Environment: linux, tomcat
            Reporter: Murali Mohan
         Attachments: Screenshot-8.png

I am trying to understand the code and may be provide some fixes/patches (example: http://jira.codehaus.org/browse/CONTINUUM-2704).
Checked out latest code from trunk (1.4.2-SNAPSHOT). Trying to execute a shell build when
it fails. StackTrace given below. This is a new build created after running the continuum-webapp
(built from trunk code) for the first time. This is not a migrated build (meaning it was a
new build defined in the fresh instance).

Screenshot of continuum UI showing the failing build (Test.sh) is also attached.

Can someone please help? What is the reason for this error?

StackTrace
=========

2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.continuum.buildmanager.ParallelBuildsManager
 - Null values set on build definition (id=6)
2013-03-05 15:42:17,691 [pool-3-thread-2] ERROR org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Unable to build project due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID
) of BUILDDEFINITION ID : 6 Please notify your system adminitrator
org.apache.continuum.buildmanager.BuildManagerException: Unable to build project due to null
values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION ID :
6 Please notify your system adminitrator
    at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
    at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
    at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
    at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
    at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
    at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
    at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
    at java.lang.Thread.run(Thread.java:662)
2013-03-05 15:42:17,692 [pool-3-thread-2] ERROR org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor
 - Error executing task
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Error executing action 'build-project'
    at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:657)
    at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.executeTask(PrepareBuildProjectsTaskExecutor.java:215)
    at org.apache.continuum.taskqueueexecutor.ParallelBuildsThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ParallelBuildsThreadedTaskQueueExecutor.java:120)
    at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442)
    at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176)
    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
    at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
    at java.lang.Thread.run(Thread.java:662)
Caused by: org.apache.continuum.buildmanager.BuildManagerException: Unable to build project
due to null values set on ( GOALS , ARGUMENTS , BUILD_FILE, SCHEDULE_ID_OID ) of BUILDDEFINITION
ID : 6 Please notify your system adminitrator
    at org.apache.continuum.buildmanager.ParallelBuildsManager.buildProjects(ParallelBuildsManager.java:193)
    at org.apache.maven.continuum.core.action.CreateBuildProjectTaskAction.execute(CreateBuildProjectTaskAction.java:123)
    at org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor.buildProjects(PrepareBuildProjectsTaskExecutor.java:647)
    ... 7 more


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=321645#comment-321645
] 

Brett Porter commented on CONTINUUM-2704:
-----------------------------------------

That certainly looks like the case, good catch. It would be necessary to confirm that the
rest of the side effects of those methods are thread safe, but a narrower synchronization
window can likely be established if needed that doesn't lock them to one at a time. Thanks
for working through this.
                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320682#comment-320682
] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

Other  Execuotr implementations do not have synchronized keyword, may be we can remove this?
                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320681#comment-320681
] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

I think this is the issue. In class ShellBuildExecutor.java in continuum-core project, I see
the following method as synchronized, that is the problem.

{code}
public synchronized ContinuumBuildExecutionResult build( Project project, BuildDefinition
buildDefinition,
                                                         File buildOutput )
    throws ContinuumBuildExecutorException
{
    // TODO: this should be validated earlier?
	
	log.info("MUR: build");
	
    String executable = getBuildFileForProject( project, buildDefinition );

    return executeShellCommand( project, executable, buildDefinition.getArguments(), buildOutput,
                                getEnvironments( buildDefinition ) );
}
{code}
                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

    [ https://jira.codehaus.org/browse/CONTINUUM-2704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320673#comment-320673
] 

Murali Mohan commented on CONTINUUM-2704:
-----------------------------------------

Log analysis and some observations:
==================================

The continuum logs when 2 shell builds attempt to run in parallel, is given below. Lines with
"MURALI:" are inserted manually by me to label what is happening, in my understanding.

The last log statement before the second build gets stuck is:
2013-03-01 13:59:40,825 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action execute-builder

The logs from the DefaultShellCommandHelper is missing. This means that the second build is
not even reaching the DefaultShellCommandHelper. This should confirm that this is a continuum
bug and not related to my installation setup.

Logs:
=========

*****MURALI: 1st build STart ******

2013-03-01 13:58:50,534 [http-9000-Processor16] INFO  org.apache.continuum.buildmanager.ParallelBuildsManager
 - Queueing prepare-build-project task 'org.apache.continuum.taskqueue.PrepareBuildProjectsTask@186'
to prepare-build queue.
2013-03-01 13:58:50,534 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Initializing prepare build
2013-03-01 13:58:50,559 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Starting prepare build of project: Cleandb_Backend_Maint
2013-03-01 13:58:50,598 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Purging existing working copy
2013-03-01 13:58:50,598 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action clean-working-directory
2013-03-01 13:58:53,149 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Updating working dir
2013-03-01 13:58:53,149 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action check-working-directory
2013-03-01 13:58:53,161 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action checkout-project
2013-03-01 13:58:53,278 [pool-13-thread-1] INFO  action#checkout-project  - Checking out project:
'Cleandb_Backend_Maint', id: '77' to '/home/continuum/continuumDirectories/trunk/working-directory/77'.
2013-03-01 13:58:53,293 [pool-13-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Executing: /bin/sh -c cd /home/continuum/continuumDirectories/trunk/working-directory &&
svn --username v963061 --password '*****' --non-interactive checkout http://labscvs.superpages.com:7151/BidCenter/bidcenter/branches/BC_72_MAINT
77
2013-03-01 13:58:53,293 [pool-13-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Working directory: /home/continuum/continuumDirectories/trunk/working-directory
2013-03-01 13:59:40,600 [pool-13-thread-1] INFO  action#checkout-project  - Checked out 2760
files.
2013-03-01 13:59:40,642 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Merging SCM results
2013-03-01 13:59:40,642 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Ending prepare build of project: Cleandb_Backend_Maint
2013-03-01 13:59:40,642 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Ending prepare build
2013-03-01 13:59:40,663 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action create-build-project-task
2013-03-01 13:59:40,738 [pool-13-thread-1] INFO  org.apache.continuum.buildmanager.ParallelBuildsManager
 - Project '77' - 'Cleandb_Backend_Maint' added to overall build queue 'MAINT_BACKEND_QUEUE'.
2013-03-01 13:59:40,739 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Initializing build
2013-03-01 13:59:40,758 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Starting build of Cleandb_Backend_Maint
2013-03-01 13:59:40,820 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - FreshBuild configured, building
2013-03-01 13:59:40,820 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action update-project-from-working-directory
2013-03-01 13:59:40,822 [pool-7-thread-17] INFO  action#update-project-from-working-directory
 - Updating project 'Cleandb_Backend_Maint' from checkout.
2013-03-01 13:59:40,825 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action execute-builder

*****1st build executing statements below ******
2013-03-01 13:59:41,000 [pool-7-thread-17] INFO  org.apache.continuum.utils.shell.DefaultShellCommandHelper
 - Executing: /bin/sh -c cd /home/continuum/continuumDirectories/trunk/working-directory/77
&& cleandb2Continuum_maint_backend.sh
2013-03-01 13:59:41,000 [pool-7-thread-17] INFO  org.apache.continuum.utils.shell.DefaultShellCommandHelper
 - Working directory: /home/continuum/continuumDirectories/trunk/working-directory/77
2013-03-01 13:59:54,771 [http-9000-Processor23] INFO  org.apache.continuum.buildmanager.ParallelBuildsManager
 - Queueing prepare-build-project task 'org.apache.continuum.taskqueue.PrepareBuildProjectsTask@198'
to prepare-build queue.

*****MURALI: 2nd build start ******
2013-03-01 13:59:54,799 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Initializing prepare build
2013-03-01 13:59:54,823 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Starting prepare build of project: Cleandb_Backend_trunk
2013-03-01 13:59:54,874 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Updating working dir
2013-03-01 13:59:54,874 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action check-working-directory
2013-03-01 13:59:54,875 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action update-working-directory-from-scm
2013-03-01 13:59:54,968 [pool-13-thread-1] INFO  action#update-working-directory-from-scm
 - Updating project: Cleandb_Backend_trunk', id: '76' to '/home/continuum/continuumDirectories/trunk/working-directory/76'.
v963061 --password '*****' --non-interactive update /home/continuum/continuumDirectories/trunk/working-directory/76
2013-03-01 13:59:54,970 [pool-13-thread-1] INFO  org.apache.continuum.scm.manager.Slf4jScmLogger
 - Working directory: /home/continuum/continuumDirectories/trunk/working-directory/76
2013-03-01 13:59:57,887 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Merging SCM results
2013-03-01 13:59:57,887 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Ending prepare build of project: Cleandb_Backend_trunk
2013-03-01 13:59:57,887 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Ending prepare build
2013-03-01 13:59:57,944 [pool-13-thread-1] INFO  org.apache.maven.continuum.scm.queue.PrepareBuildProjectsTaskExecutor
 - Performing action create-build-project-task
2013-03-01 13:59:57,962 [pool-13-thread-1] INFO  org.apache.continuum.buildmanager.ParallelBuildsManager
 - Project '76' - 'Cleandb_Backend_trunk' added to overall build queue 'TRUNK_BACKEND_QUEUE'.
2013-03-01 13:59:57,962 [pool-5-thread-16] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Initializing build
2013-03-01 13:59:57,980 [pool-5-thread-16] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Starting build of Cleandb_Backend_trunk
2013-03-01 13:59:58,009 [pool-5-thread-16] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - AlwaysBuild configured, building
2013-03-01 13:59:58,009 [pool-5-thread-16] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action update-project-from-working-directory
2013-03-01 13:59:58,011 [pool-5-thread-16] INFO  action#update-project-from-working-directory
 - Updating project 'Cleandb_Backend_trunk' from checkout.
2013-03-01 13:59:58,014 [pool-5-thread-16] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action execute-builder

*****MURALI: 2nd build executing statements MISSING FOR SOME TIME, it is waiting for 1st build
to finish ******
2013-03-01 14:01:20,730 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,836 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,845 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,861 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,879 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,879 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:01:20,879 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'removePrepareBuildEntries.action' in namespace:
''. Form action defaulting to 'action' attribute's literal value.
2013-03-01 14:01:20,879 [http-9000-Processor16] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'removePrepareBuildEntries.action' in namespace:
''. Form action defaulting to 'action' attribute's literal value.
2013-03-01 14:01:54,204 [pool-7-thread-17] INFO  org.apache.maven.continuum.execution.shell.ShellBuildExecutor
 - Exit code: 0

*****MURALI: 2nd build executing statements NOW, after 1st build ends ******
2013-03-01 14:01:54,206 [pool-5-thread-16] INFO  org.apache.continuum.utils.shell.DefaultShellCommandHelper
 - Executing: /bin/sh -c cd /home/continuum/continuumDirectories/trunk/working-directory/76
&& cleandb2Continuum_trunk_backend.sh
2013-03-01 14:01:54,206 [pool-5-thread-16] INFO  org.apache.continuum.utils.shell.DefaultShellCommandHelper
 - Working directory: /home/continuum/continuumDirectories/trunk/working-directory/76
2013-03-01 14:01:54,484 [pool-7-thread-17] INFO  org.apache.maven.continuum.buildcontroller.DefaultBuildController
 - Performing action deploy-artifact
2013-03-01 14:02:21,697 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,699 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,699 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,700 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,700 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,700 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'none' in namespace: ''. Form action defaulting
to 'action' attribute's literal value.
2013-03-01 14:02:21,700 [http-9000-Processor23] WARN  org.apache.struts2.components.Form 
- No configuration found for the specified action: 'removePrepareBuildEntries.action' in namespace:
''. Form action defaulting to 'action' attribute's literal value.
2013-03-01 14:02:21,700 [http-9000-Processor23] WARN  org.apache.s




                
> Shell builds are not executing concurrently
> -------------------------------------------
>
>                 Key: CONTINUUM-2704
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
>             Project: Continuum
>          Issue Type: Bug
>          Components: Parallel Builds
>    Affects Versions: 1.3.8
>         Environment: Ubuntu, Tomcat
>            Reporter: Murali Mohan
>
> Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.
> I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.
> The problem is that, when the shell build from A runs, it will not execute the build
until the shell build from B is complete. it is almost  like A is waiting for B to finish.
Please note that maven builds are happily running in parallel in these 2 queues. It is only
the shell build that has a problem.
> To be sure that this is not an OS level problem, I started the build in B from Continuum
and ran the shell script for A from command line and it worked fine - both ran in parallel.
So, I think Continuum has a bottle neck somewhere. please help.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Murali Mohan created CONTINUUM-2704:
---------------------------------------

             Summary: Shell builds are not executing concurrently
                 Key: CONTINUUM-2704
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2704
             Project: Continuum
          Issue Type: Bug
          Components: Parallel Builds
    Affects Versions: 1.3.8
         Environment: Ubuntu, Tomcat
            Reporter: Murali Mohan



Continuum version 1.3.6. Deployed on Tomcat in Ubuntu.

I have 2 projects, say A and B. Each has shell builds defined and set to run in different
queues. Number of parallel builds is set to 4.

The problem is that, when the shell build from A runs, it will not execute the build until
the shell build from B is complete. it is almost  like A is waiting for B to finish. Please
note that maven builds are happily running in parallel in these 2 queues. It is only the shell
build that has a problem.

To be sure that this is not an OS level problem, I started the build in B from Continuum and
ran the shell script for A from command line and it worked fine - both ran in parallel. So,
I think Continuum has a bottle neck somewhere. please help.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

     [ https://jira.codehaus.org/browse/CONTINUUM-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-2703.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.2
         Assignee: Brett Porter
    
> reduce logging from RbacAuthorizer
> ----------------------------------
>
>                 Key: CONTINUUM-2703
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2703
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.4.2
>
>
> When attempting to resolve permissions, there are several trace statements logged at
info level:
> * permission map does not contain operation
> * no permission found for operation
> These were changed to debug level on redback trunk, and should be the same in Continuum
as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

    [ https://jira.codehaus.org/browse/CONTINUUM-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=319853#comment-319853
] 

Brett Porter commented on CONTINUUM-2703:
-----------------------------------------

Reduced the level to WARN, but that could be reverted if using a more recent version of Redback
(applied to both 1.3-M3-SNAPSHOT and Redback trunk)
                
> reduce logging from RbacAuthorizer
> ----------------------------------
>
>                 Key: CONTINUUM-2703
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2703
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>            Priority: Minor
>             Fix For: 1.4.2
>
>
> When attempting to resolve permissions, there are several trace statements logged at
info level:
> * permission map does not contain operation
> * no permission found for operation
> These were changed to debug level on redback trunk, and should be the same in Continuum
as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Brett Porter created CONTINUUM-2703:
---------------------------------------

             Summary: reduce logging from RbacAuthorizer
                 Key: CONTINUUM-2703
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2703
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.4.1
            Reporter: Brett Porter
            Priority: Minor


When attempting to resolve permissions, there are several trace statements logged at info
level:
* permission map does not contain operation
* no permission found for operation

These were changed to debug level on redback trunk, and should be the same in Continuum as
well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-2085.
-----------------------------------

    Resolution: Duplicate
    
> Project name is changed when run a build in a child project
> -----------------------------------------------------------
>
>                 Key: CONTINUUM-2085
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2085
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.3.1 (Alpha)
>         Environment: All environments
>            Reporter: Antonio Manuel Muñiz Martín
>            Priority: Minor
>              Labels: backlog-to-cleanup
>         Attachments: build-definition.png
>
>
> With a simple multimodule project like:
> project
> -- pom.xml
> -- child1
>     --pom.xml
> -- child2
>     --pom.xml
> If exists a build that acts in a child project (in "Build file input" appears "child1/pom.xml"),
when this build is throwed the name of the project is changed, the new name is the child name.
> (I have attached an image to show it).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ https://jira.codehaus.org/browse/CONTINUUM-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-2465.
-----------------------------------

    Resolution: Duplicate
      Assignee: Brett Porter

In 1.4.1, build definitions can now control whether they update project information from SCM.
                
> Project Name gets reset when build occurs
> -----------------------------------------
>
>                 Key: CONTINUUM-2465
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2465
>             Project: Continuum
>          Issue Type: Bug
>         Environment: Version: 1.3.4-SNAPSHOT
> Build Number: 	790494
>            Reporter: SebbASF
>            Assignee: Brett Porter
>              Labels: backlog-to-cleanup
>
> The Project Information screen allows one to change the project name.
> This is useful for e.g. Apache Commons, which has two versions of Lang currently.
> However, when the project is built, the project name is reset to the original.
> If the name can be changed on the Info screen, then surely changes should be retained?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

    [ https://jira.codehaus.org/browse/CONTINUUM-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318703#comment-318703
] 

Brett Porter commented on CONTINUUM-2702:
-----------------------------------------

Thanks for reporting this, some of the validations are certainly too aggressive. Do you mind
submitting this fix in patch format, with tests to verify it to ensure that it is not lost
in future? You'll find examples of other validations rules in the projects mentioned and continuum-webapp-test
                
> Cannot add an argument to remove a profile ( -P!profile) 
> ---------------------------------------------------------
>
>                 Key: CONTINUUM-2702
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2702
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web interface, XMLRPC Interface
>    Affects Versions: 1.4.1
>         Environment: All
>            Reporter: edward grey
>             Fix For: 1.4.2
>
>
> I've a maven profile 'dev' in my project for local configuration. 
> When I build my project, I want to remove the dev profile. maven provides the -P!dev
command. In continuum version 1.3.4, adding this attribute was OK.
> In v1.4.1, there is an error ('!' detected as invalid character). 
> To fix this, we should add '!' in the list of accepted character in 3 files :
> continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/BuildDefinitionAction-saveBuildDefinition-validation.xml
> continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/admin/BuildDefinitionTemplateAction-saveBuildDefinitionAsTemplate-validation.xml
> continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-server/src/main/java/org/apache/maven/continuum/xmlrpc/server/ContinuumServiceImpl.java
> In this 3 files, the argument validation pattern should accept '!'.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2702:
------------------------------------

    Fix Version/s: 1.4.2
    
> Cannot add an argument to remove a profile ( -P!profile) 
> ---------------------------------------------------------
>
>                 Key: CONTINUUM-2702
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2702
>             Project: Continuum
>          Issue Type: Bug
>          Components: Web interface, XMLRPC Interface
>    Affects Versions: 1.4.1
>         Environment: All
>            Reporter: edward grey
>             Fix For: 1.4.2
>
>
> I've a maven profile 'dev' in my project for local configuration. 
> When I build my project, I want to remove the dev profile. maven provides the -P!dev
command. In continuum version 1.3.4, adding this attribute was OK.
> In v1.4.1, there is an error ('!' detected as invalid character). 
> To fix this, we should add '!' in the list of accepted character in 3 files :
> continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/BuildDefinitionAction-saveBuildDefinition-validation.xml
> continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/admin/BuildDefinitionTemplateAction-saveBuildDefinitionAsTemplate-validation.xml
> continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-server/src/main/java/org/apache/maven/continuum/xmlrpc/server/ContinuumServiceImpl.java
> In this 3 files, the argument validation pattern should accept '!'.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

edward grey created CONTINUUM-2702:
--------------------------------------

             Summary: Cannot add an argument to remove a profile ( -P!profile) 
                 Key: CONTINUUM-2702
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2702
             Project: Continuum
          Issue Type: Bug
          Components: Web interface, XMLRPC Interface
    Affects Versions: 1.4.1
         Environment: All
            Reporter: edward grey


I've a maven profile 'dev' in my project for local configuration. 
When I build my project, I want to remove the dev profile. maven provides the -P!dev command.
In continuum version 1.3.4, adding this attribute was OK.

In v1.4.1, there is an error ('!' detected as invalid character). 

To fix this, we should add '!' in the list of accepted character in 3 files :
continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/BuildDefinitionAction-saveBuildDefinition-validation.xml

continuum/trunk/continuum-webapp/src/main/resources/org/apache/maven/continuum/web/action/admin/BuildDefinitionTemplateAction-saveBuildDefinitionAsTemplate-validation.xml

continuum/trunk/continuum-xmlrpc/continuum-xmlrpc-server/src/main/java/org/apache/maven/continuum/xmlrpc/server/ContinuumServiceImpl.java


In this 3 files, the argument validation pattern should accept '!'.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

    [ https://jira.codehaus.org/browse/CONTINUUM-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317908#comment-317908
] 

Brett Porter commented on CONTINUUM-2701:
-----------------------------------------

Thanks for the report - this certainly shouldn't happen. 
                
> Legacy projects with ampersand lack permission after upgrade
> ------------------------------------------------------------
>
>                 Key: CONTINUUM-2701
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2701
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.4.1
>            Reporter: Philippe Busque
>
> I upgraded Continuum from 1.3.6 to 1.4.1
> Some of my projets had ampersand in their name. In 1.3.X, this was allowed.
> Now in 1.4.1, the interface block you from creating project with ampersand in their name.
However, for every project with ampersand already in their name, those project are locked
out.
> When opening the project, the following message is displayed :
> Authorization Error
> You are not authorized to access this page. Please contact your administrator to be granted
the appropriate permissions.
> In the logs, the following trace is displayed:
>  INFO  org.codehaus.plexus.redback.authorization.rbac.RbacAuthorizer  - no permission
found for operation continuum-view-group resource Questions & Answers

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Philippe Busque created CONTINUUM-2701:
------------------------------------------

             Summary: Legacy projects with ampersand lack permission after upgrade
                 Key: CONTINUUM-2701
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2701
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.4.1
            Reporter: Philippe Busque


I upgraded Continuum from 1.3.6 to 1.4.1
Some of my projets had ampersand in their name. In 1.3.X, this was allowed.

Now in 1.4.1, the interface block you from creating project with ampersand in their name.
However, for every project with ampersand already in their name, those project are locked
out.

When opening the project, the following message is displayed :
Authorization Error
You are not authorized to access this page. Please contact your administrator to be granted
the appropriate permissions.

In the logs, the following trace is displayed:
 INFO  org.codehaus.plexus.redback.authorization.rbac.RbacAuthorizer  - no permission found
for operation continuum-view-group resource Questions & Answers



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Brett Porter created CONTINUUM-2700:
---------------------------------------

             Summary: SystemConfiguration in XMLRPC API is not populated from continuum.xml
contents
                 Key: CONTINUUM-2700
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2700
             Project: Continuum
          Issue Type: Bug
          Components: XMLRPC Interface
    Affects Versions: 1.4.1
            Reporter: Brett Porter


The getSystemConfiguration() call only looks at the DAO, which is no longer populated with
the contents stored in the file. It should return the appropriate fallback for the file and
default.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-2699.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.4.2
         Assignee: Brett Porter
    
> Document installing Continuum as a Mac OS X service with launchd
> ----------------------------------------------------------------
>
>                 Key: CONTINUUM-2699
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2699
>             Project: Continuum
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Brett Porter
>            Assignee: Brett Porter
>             Fix For: 1.4.2
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Brett Porter created CONTINUUM-2699:
---------------------------------------

             Summary: Document installing Continuum as a Mac OS X service with launchd
                 Key: CONTINUUM-2699
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2699
             Project: Continuum
          Issue Type: Bug
          Components: Documentation
            Reporter: Brett Porter




--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter closed CONTINUUM-2698.
-----------------------------------

    Resolution: Fixed
      Assignee: Brett Porter

Removed the contents, but don't have permissions to fix the directory or the archives. Please
file such requests in the INFRA tracker in future...
                
> Delete obsolete download files
> ------------------------------
>
>                 Key: CONTINUUM-2698
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2698
>             Project: Continuum
>          Issue Type: Task
>            Reporter: SebbASF
>            Assignee: Brett Porter
>
> There is still a directory structure on minotaur under 
> /www/www.apache.org/dist/continuum-prepubsub
> This entire directory tree should now be deleted please.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

    [ https://jira.codehaus.org/browse/CONTINUUM-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317091#comment-317091
] 

Brett Porter commented on CONTINUUM-2698:
-----------------------------------------

I'll check with infra why it's there
                
> Delete obsolete download files
> ------------------------------
>
>                 Key: CONTINUUM-2698
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2698
>             Project: Continuum
>          Issue Type: Task
>            Reporter: SebbASF
>
> There is still a directory structure on minotaur under 
> /www/www.apache.org/dist/continuum-prepubsub
> This entire directory tree should now be deleted please.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

SebbASF created CONTINUUM-2698:
----------------------------------

             Summary: Delete obsolete download files
                 Key: CONTINUUM-2698
                 URL: https://jira.codehaus.org/browse/CONTINUUM-2698
             Project: Continuum
          Issue Type: Task
            Reporter: SebbASF


There is still a directory structure on minotaur under 

/www/www.apache.org/dist/continuum-prepubsub

This entire directory tree should now be deleted please.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2609:
------------------------------------

    Fix Version/s:     (was: 1.4.1)
    
> Unable to delete a project, getting an invalid group id
> -------------------------------------------------------
>
>                 Key: CONTINUUM-2609
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2609
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system
>    Affects Versions: 1.4.1
>            Reporter: Maria Catherine Tan
>            Assignee: Maria Catherine Tan
>
> From the continuum project group page, select a project and then click "Delete Project(s)"
button
> org.apache.maven.continuum.ContinuumException: invalid group id
> 	at org.apache.maven.continuum.DefaultContinuum.getProjectGroup(DefaultContinuum.java:340)
> 	at org.apache.maven.continuum.web.action.ProjectsListAction.getProjectGroupName(ProjectsListAction.java:200)
> 	at org.apache.maven.continuum.web.action.ProjectsListAction.remove(ProjectsListAction.java:91)
> 	at org.apache.maven.continuum.web.action.ProjectsListAction.execute(ProjectsListAction.java:76)
> 	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:597)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:440)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:279)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:242)
> 	at org.apache.struts2.interceptor.MessageStoreInterceptor.intercept(MessageStoreInterceptor.java:204)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:163)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:249)
> 	at org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.doIntercept(AnnotationValidationInterceptor.java:68)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:70)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.codehaus.plexus.redback.struts2.interceptor.PolicyEnforcementInterceptor.intercept(PolicyEnforcementInterceptor.java:159)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.codehaus.plexus.redback.struts2.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:173)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:163)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:249)
> 	at org.apache.struts2.interceptor.validation.AnnotationValidationInterceptor.doIntercept(AnnotationValidationInterceptor.java:68)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ConversionErrorInterceptor.intercept(ConversionErrorInterceptor.java:122)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:195)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ParametersInterceptor.doIntercept(ParametersInterceptor.java:195)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.StaticParametersInterceptor.intercept(StaticParametersInterceptor.java:148)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.interceptor.CheckboxInterceptor.intercept(CheckboxInterceptor.java:93)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.interceptor.FileUploadInterceptor.intercept(FileUploadInterceptor.java:235)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ModelDrivenInterceptor.intercept(ModelDrivenInterceptor.java:89)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ScopedModelDrivenInterceptor.intercept(ScopedModelDrivenInterceptor.java:128)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.interceptor.ProfilingActivationInterceptor.intercept(ProfilingActivationInterceptor.java:104)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.interceptor.debugging.DebuggingInterceptor.intercept(DebuggingInterceptor.java:267)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ChainingInterceptor.intercept(ChainingInterceptor.java:126)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.PrepareInterceptor.doIntercept(PrepareInterceptor.java:138)
> 	at com.opensymphony.xwork2.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:87)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.I18nInterceptor.intercept(I18nInterceptor.java:148)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.interceptor.ServletConfigInterceptor.intercept(ServletConfigInterceptor.java:164)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.AliasInterceptor.intercept(AliasInterceptor.java:128)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at com.opensymphony.xwork2.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:176)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.codehaus.plexus.redback.struts2.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.java:169)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.codehaus.plexus.redback.struts2.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInterceptor.java:77)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.codehaus.plexus.redback.struts2.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckInterceptor.java:97)
> 	at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:236)
> 	at org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:52)
> 	at org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:468)
> 	at org.apache.struts2.dispatcher.ng.ExecuteOperations.executeAction(ExecuteOperations.java:77)
> 	at org.apache.struts2.dispatcher.ng.filter.StrutsExecuteFilter.doFilter(StrutsExecuteFilter.java:76)
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
> 	at com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
> 	at org.apache.struts2.dispatcher.ng.filter.StrutsPrepareFilter.doFilter(StrutsPrepareFilter.java:65)
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
> 	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:96)
> 	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1148)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:387)
> 	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> 	at org.mortbay.jetty.Server.handle(Server.java:326)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
> 	at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
> 	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:451)
> Caused by: org.apache.maven.continuum.store.ContinuumObjectNotFoundException: Could not
find object. Type 'org.apache.maven.continuum.model.project.ProjectGroup'. Id: '0'.
> 	at org.apache.continuum.dao.AbstractDao.getObjectById(AbstractDao.java:116)
> 	at org.apache.continuum.dao.AbstractDao.getObjectById(AbstractDao.java:104)
> 	at org.apache.continuum.dao.ProjectGroupDaoImpl.getProjectGroup(ProjectGroupDaoImpl.java:121)
> 	at org.apache.maven.continuum.DefaultContinuum.getProjectGroup(DefaultContinuum.java:336)
> 	... 102 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

     [ https://jira.codehaus.org/browse/CONTINUUM-2552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter updated CONTINUUM-2552:
------------------------------------

    Fix Version/s:     (was: 1.4.1)
    
> JDOException when deleting a project
> ------------------------------------
>
>                 Key: CONTINUUM-2552
>                 URL: https://jira.codehaus.org/browse/CONTINUUM-2552
>             Project: Continuum
>          Issue Type: Bug
>          Components: Core system, Database
>    Affects Versions: 1.4.0 (Beta)
>            Reporter: Maria Catherine Tan
>
> We already set the parent to null, cleared project dependency and modified dependencies
of build result but there are times that Continuum is still throwing a JDOException when deleting
a project.
> Maybe setting the build result's project to null before removing the build result might
help.
> Error Occured
> javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables:
javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM `PROJECTDEPENDENCY` WHERE
`PROJECTDEPENDENCY_ID`=? NestedThrowables: com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException:
Cannot delete or update a parent row: a foreign key constraint fails (`continuum107`.`PROJECT`,
CONSTRAINT `PROJECT_FK1` FOREIGN KEY (`PARENT_PROJECTDEPENDENCY_ID_OID`) REFERENCES `PROJECTDEPENDENCY`
(`PROJECTDEPENDENCY_ID`)) 
> Show/hide Stack Trace
>         javax.jdo.JDOUserException: One or more instances could not be deleted
> 	at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersistenceManager.java:1541)
> 	at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersistenceManager.java:1514)
> 	at org.jpox.store.rdbms.scostore.FKListStore.clear(FKListStore.java:1137)
> 	at org.jpox.store.mapping.CollectionMapping.deleteDependent(CollectionMapping.java:334)
> 	at org.jpox.store.rdbms.table.ClassTable.deleteDependent(ClassTable.java:2651)
> 	at org.jpox.store.StoreManager.deleteDependent(StoreManager.java:1076)
> 	at org.jpox.state.StateManagerImpl.deletePersistent(StateManagerImpl.java:4405)
> 	at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPersistenceManager.java:1489)
> 	at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistenceManager.java:1505)
> 	at org.codehaus.plexus.jdo.PlexusJdoUtils.removeObject(PlexusJdoUtils.java:121)
> 	at org.apache.continuum.dao.AbstractDao.removeObject(AbstractDao.java:95)
> 	at org.apache.continuum.dao.BuildResultDaoImpl.removeBuildResult(BuildResultDaoImpl.java:311)
> 	at org.apache.maven.continuum.DefaultContinuum.removeBuildResult(DefaultContinuum.java:1108)
> 	at org.apache.maven.continuum.DefaultContinuum.removeProject(DefaultContinuum.java:689)
> 	at org.apache.maven.continuum.web.action.DeleteProjectAction.execute(DeleteProjectAction.java:83)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira