Maven SCM

Continuum fails while trying to build from clearcase

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 1.0-beta-3
  • Fix Version/s: future
  • Component/s: maven-scm-provider-clearcase
  • Labels:
    None
  • Environment:
    Clearcase UCM / Windows XP / Snapshot view
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

When trying to perform a build from continuum I receive the following error:

Provider message: The cleartool command failed.
Command output:
-------------------------------------------------------------------------------
cleartool: Error: A registry entry already exists for "dandendj-LNGDAYD-4130684-maven-7".
-------------------------------------------------------------------------------
This happens on the second time through. On the first time through I receive:

org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Could not find Maven project descriptor.
at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:111)
at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:62)
at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:169)
at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:53)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103)
at java.lang.Thread.run(Thread.java:595)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
David Dandeneau added a comment -

I also receive the error:

-------------------------------------------------------------------------------
cleartool: Error: A registry entry already exists for "dandendj-LNGDAYD-4130684-XXX".
-------------------------------------------------------------------------------

while performing a release:perform.

Show
David Dandeneau added a comment - I also receive the error: ------------------------------------------------------------------------------- cleartool: Error: A registry entry already exists for "dandendj-LNGDAYD-4130684-XXX". ------------------------------------------------------------------------------- while performing a release:perform.
Hide
Permalink
Kjetil Ødegaard added a comment -

I don't know if this is related, but I also get the "A registry entry already exists" every time I try to build a ClearCase project from Continuum. "scm:update" works fine from the command line.

Show
Kjetil Ødegaard added a comment - I don't know if this is related, but I also get the "A registry entry already exists" every time I try to build a ClearCase project from Continuum. "scm:update" works fine from the command line.
Hide
Permalink
Kalle Korhonen added a comment -

This still happens in 1.0.3. My Clearcase master build works, but sub-module builds and builds from different branches fail with the same exception. I'm building on Linux w/ standard Clearcase 6.x.

Show
Kalle Korhonen added a comment - This still happens in 1.0.3. My Clearcase master build works, but sub-module builds and builds from different branches fail with the same exception. I'm building on Linux w/ standard Clearcase 6.x.
Hide
Permalink
Kalle Korhonen added a comment -

Don't know what the root cause of the problem is but, sometimes the actual build directory isn't created while the view storage directory is. To work around the problem, you can remove the created view storage dir with "cleartool rmview" (check the id of the Continuum build to know which one to remove) and then try again. Once Continuum is happy with the directories and doesn't try re-creating snapshot, but uses update only, the problem is gone.

Show
Kalle Korhonen added a comment - Don't know what the root cause of the problem is but, sometimes the actual build directory isn't created while the view storage directory is. To work around the problem, you can remove the created view storage dir with "cleartool rmview" (check the id of the Continuum build to know which one to remove) and then try again. Once Continuum is happy with the directories and doesn't try re-creating snapshot, but uses update only, the problem is gone.
Hide
Permalink
Emmanuel Venisse added a comment -

you can look at clearcase scm provider. If you don't provide a solution for your pb in clearcase provider, we'll can't fix it.

Show
Emmanuel Venisse added a comment - you can look at clearcase scm provider. If you don't provide a solution for your pb in clearcase provider, we'll can't fix it.

People

  • Assignee:
    Unassigned
    Reporter:
    David Dandeneau
Vote (4)
Watch (2)

Dates

  • Created:
    Updated: