Skip to content
Laurent Petit edited this page Mar 20, 2015 · 1 revision

Software Update Sites

What are the different available update sites for installing Counterclockwise?

Software Update Sites as stability Channels

Counterclockwise can be installed from several Software Update Site URLs.

You can draw an analogy between these different update site URLs and the different "channels" that are available for updating Google Chrome, for instance.

  • Stable Releases Software Update Site: http://updatesite.ccw-ide.org/stable/ ( legacy: http://ccw.cgrand.net/updatesite/ )
Promotion to this Update Site is manual. 
Retention policy: versions included here stay forever.
  • Beta Releases Software Update Site: http://updatesite.ccw-ide.org/beta/ ( legacy: http://ccw.cgrand.net/updatesite-betas/ )
Contains intermediate versions between 2 releases, for which I would like user feedback. 
Promotion to this Update Site is manual.
Retention policy: intermediate versions (between 2 stable versions) retained until new stable version.
  • Per-branch Latest Continuous Integration Build Software Update Site: http://updatesite.ccw-ide.org/branch/<branch-name>/
Promotion to this Update Site is automatic, each time an [OpenJDK7, Juno] of the branch tip Build succeeds on Travis.
Retention policy: each new successful build overwrites the old version.

Direct Access to individual builds

Any version available in the stable / beta / per-branch-ci update sites has a stable (*) direct access url of the form http://updatesite.ccw-ide.org/branch/<branch-name>/<branch-name>-travis<build_number>-git<sha1>

Self contained Counterclockwise Product

Each version built also contains Eclipse Products pre-packaging Counterclockwise plus a lot of other common features (Git, Maven, CSS, HTML support, etc.).

Products are platform dependent and built for the most common ones nowadays: Windows 32bits, Windows 64bits, Linux 32bits, Linux 64bits, OS X 64bits

They are available at URLs of the form: http://updatesite.ccw-ide.org/branch/<branch-name>/<branch-name>-travis<build_number>-git<sha1>/products/

(*) as long as the retention policy implies