Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 324451 - Make ripplor restartable
Summary: Make ripplor restartable
Status: CLOSED WONTFIX
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 387888
Blocks:
  Show dependency tree
 
Reported: 2010-09-03 12:21 EDT by Steve Powell CLA
Modified: 2015-06-03 06:50 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Powell CLA 2010-09-03 12:21:48 EDT 
Ripplor (ripplor.rb in web-server/scripts) currently has no restart facility. Thus if a build fails in the ripple then it is hard to gather all the versions and restart the ripple from the failing point.

It is relatively easy to fix this:

just before getting and building a repo, the current list of variables and the next repo to build is deposited in a status file (ripple-status.txt).

In normal operation this is left around at the end (it is also a handy summary of all the versions considered and gathered in the last ripple).

If a ripple is started and this file exists then Ripplor should prompt to see if the ripple should be restarted.  Yes means that the status log is used to augment the normal input parameters (if any) and the ripple is started from the (final) new point.

No means that the file is cleared before starting the ripple with just the input parameters.

This code can go entirely in the Ripplor script and not have any effect on the rest of the script code.
Comment 1 Florian Waibel CLA 2015-06-03 06:50:00 EDT 
With the introduction of virgo-root and the switch to Gradle (Bug 463462) this seems obsolete, now.