Add an admin task to stop properly Continuum

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: 1.4.2 (Beta)
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate

Description

When a project is building and an admin stop continuum, the actual build result is never marked as stopped.

A possible solution would be to planned a shutdown in the web interface via a form. With this action, all sheduler will be stopped and a message will be sent to the admin (page after the submit in the shutdown form). With this message, the admin will know that he can shutdown Continuum properly without non ended build process.

Issue Links

relates to

New Feature - A new feature of the product, which has yet to be developed. CONTINUUM-2098 Provide a Web UI for database backup and restore

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

couldn't this be a shutdown hook? I would even think that the Disposable interface on the plexus components would work for this (which is implemented in the spring layer too now).

Show
Brett Porter added a comment - couldn't this be a shutdown hook? I would even think that the Disposable interface on the plexus components would work for this (which is implemented in the spring layer too now).
Hide
Permalink
Wendy Smoak added a comment -

This is definitely necessary, and should be available in some way that supports scripting.

It needs to stop accepting requests, stop scheduling things, and shut down once the queues are empty.

There should be a (configurable) timeout so that it doesn't wait forever. (Maybe you're trying to shut down because a build is stuck and will never finish.)

Show
Wendy Smoak added a comment - This is definitely necessary, and should be available in some way that supports scripting. It needs to stop accepting requests, stop scheduling things, and shut down once the queues are empty. There should be a (configurable) timeout so that it doesn't wait forever. (Maybe you're trying to shut down because a build is stuck and will never finish.)

People

  • Assignee:
    Unassigned
    Reporter:
    Emmanuel Venisse
Vote (3)
Watch (2)

Dates

  • Created:
    Updated: