jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Continuum
  • CONTINUUM-1642

"Failed to rollback release" when no SNAPSHOT version was defined

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.1
  • Fix Version/s: None
  • Component/s: Core system
  • Labels:
    None
  • Environment:
    OS: Linux
    Java: 1.5
  • Complexity:
    Intermediate

Description

When you have a project without SNAPSHOT versions the release and rollback functionality is broken. For example with our company POM we increment version whenever a change is done, snapshots are never used. When I try to release a new version with continuum the release-prepare fails, saying that no SNAPSHOT is defined. This could eventually be ok. But doing a rollback afterwards freeces the web-UI with an TaskExecutionException in the logs:

ERROR org.codehaus.plexus.taskqueue.execution.TaskQueueExecutor:rollback-release - Error executing task
org.codehaus.plexus.taskqueue.execution.TaskExecutionException: Failed to rollback release
at org.apache.maven.continuum.release.executors.RollbackReleaseTaskExecutor.execute(RollbackReleaseTaskExecutor.java:45)
at org.apache.maven.continuum.release.executors.AbstractReleaseTaskExecutor.executeTask(AbstractReleaseTaskExecutor.java:67)
at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116)
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$Worker.runTask(ThreadPoolExecutor.java:665)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.maven.shared.release.ReleaseExecutionException: Cannot restore from a missing backup POM: /srv/ci/continuum-1.1/apps/continuum/webapp/WEB-INF/working-director
y/13/pom.xml.releaseBackup
at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.restorePomBackup(RestoreBackupPomsPhase.java:90)
at org.apache.maven.shared.release.phase.RestoreBackupPomsPhase.execute(RestoreBackupPomsPhase.java:69)
at org.apache.maven.shared.release.DefaultReleaseManager.rollback(DefaultReleaseManager.java:248)
at org.apache.maven.continuum.release.executors.RollbackReleaseTaskExecutor.execute(RollbackReleaseTaskExecutor.java:40)
... 7 more

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1650 Cannot rollback release if prepare failed before create-backup-poms

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1887 Release rollback hangs when the release failed at the scm-check-modifications phase

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Wendy Smoak added a comment - 09/Sep/09 4:25 PM

Tested in 1.3.4 with a non-snapshot versioned project, and I still get the error in the logs, but the UI does not freeze. After clicking Rollback and then confirming, it returns me to the 'Choose Release Goal' page.

Ideally it would be smarter about whether a rollback is necessary and/or exactly what needs to be done based on the step at which the release failed.

Show
Wendy Smoak added a comment - 09/Sep/09 4:25 PM Tested in 1.3.4 with a non-snapshot versioned project, and I still get the error in the logs, but the UI does not freeze. After clicking Rollback and then confirming, it returns me to the 'Choose Release Goal' page. Ideally it would be smarter about whether a rollback is necessary and/or exactly what needs to be done based on the step at which the release failed.

People

  • Assignee:
    Wendy Smoak
    Reporter:
    Martin Höller
Vote (0)
Watch (1)

Dates

  • Created:
    01/Feb/08 2:06 AM
    Updated:
    09/Sep/09 4:25 PM
    Resolved:
    09/Sep/09 4:25 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.