[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[virgo-dev] What does the commit text '[RIPPLOR] Updated versions' mean?

Changes to the Ripplor.rb script.

I have updated the Ripple ruby scripts (see web-server/scripts) so that ripple builds now work even though some git repositories are in git.eclipse.org<http://git.eclipse.org> and some are still in git.springsource.org<http://git.springsource.org> (having not been transferred yet).  We tentatively call these 'hybrid ripples'.  Find out more about ripples at Rippling<http://wiki.eclipse.org/Virgo/Build#.22Rippling.22> on the Virgo - wiki/Build pages.

Hybrid ripples will not last forever, and are needed only in the transition period.  However, this may be the first time you have seen commits in the git repositories with text [RIPPLOR] Updated versions. Hence this note.

The first successful hybrid ripple was run last night and resulted in commits like:

SHA:     637b977f366bd4f6d2656065f067d037cdd9aab6
Author:  Steve Powell <spowell@xxxxxxxxxx<mailto:spowell@xxxxxxxxxx>>
Date:    Wed May 12 2010 17:16:20 GMT+0100 (BST)
Subject: [RIPPLOR] Updated versions
Parent:  bc109722d55c31368d92a13f66f21a01c96636a6

[RIPPLOR] Updated versions
changed:
  build.versions
  org.eclipse.virgo.kernel.agent.dm/.classpath
  org.eclipse.virgo.kernel.artifact/.classpath
  org.eclipse.virgo.kernel.core/.classpath
  org.eclipse.virgo.kernel.deployer.dm/.classpath
  org.eclipse.virgo.kernel.deployer.test/.classpath
  org.eclipse.virgo.kernel.deployer/.classpath
  org.eclipse.virgo.kernel.dm/.classpath
  org.eclipse.virgo.kernel.dmfragment/.classpath
  org.eclipse.virgo.kernel.kerneldmfragment/.classpath
  org.eclipse.virgo.kernel.model/.classpath
  org.eclipse.virgo.kernel.osgi/.classpath
  org.eclipse.virgo.kernel.services/.classpath
  org.eclipse.virgo.kernel.shell/.classpath
  org.eclipse.virgo.kernel.smoketest/.classpath
  org.eclipse.virgo.kernel.stubs/.classpath
  org.eclipse.virgo.kernel.test/.classpath
  org.eclipse.virgo.kernel.userregion/.classpath
appearing in the Git repositories.

The changes are to version information for dependencies. It is these dependencies, used for build and run-time resolution, which are the reason for the ripple process.  Rippling (up a chain of repositories) ensures that all external dependencies' versions agree, and internal dependencies use compatible build-versions.  The commits (like the one above) are automatically created and pushed by Ripplor after the version information is detected, accumulated and updated.

At present you need committer rights on the repositories to run the ripple script (it uses ssh to access the git repositories on both git servers).

As background, the most recent ripple was required to incorporate a fix to a bug (which caused pickup to be cleared intermittently!)  in util; and the right version of util should now be picked up by all the other builds.  Since usage in the other repos was also changed (using new interfaces in util) the ripple was needed before the dependants could be fixed.

Regards,
Steve Powell
[W:+44-2380-111-528; M: +44-7815-838-558; H:+44-1962-775-598]

Cannelloni n. A narrow boat for one. [SPD]
Verisimilitude adj. Extremely evenly masticated. [SPD]
Decrepit v. To muck-out the Royal stable. [SPD]