>> Monday, December 06, 2010
I tried to update to the latest integration build last week. I couldn't because I had accidentally updated to a nightly build at some point. This problem wouldn't happen to most users because only the Eclipse and Indigo repositories are defined by default in the SDK. I have many repositories defined in my install because I'm always testing bugs in different test repos.
Eclipse bundles have four part version numbers. Major.minor.service.qualifier. With a nightly build, the qualifiers of all our bundles is replaced with the build id. For example, here's a subset of the bundles from a recent nightly build. Note the qualifier is always N20101201-2000.
With an integration build, the qualifier of the bundle reflects the CVS tag that the developer submitted to the map file. Looking at at subset of bundles from the latest integration build, note that the p2.garbagecollector bundle has a qualifier of v201011-2100.
Since the first three segments of the bundle's version match, and N > v, the bundles from the nightly build always sort higher. This caveat also extends to the IU of the product id, in my case, the org.eclipse.sdk product id. Since I had accidentally upgraded to a nightly build, I couldn't update to any future integration builds because it's bundles will always sort lower.
No problem, I thought. I'll just revert to an earlier install. That's one of the many things that I love about p2. Because p2 stores your previous profiles in the profile registry, you can revert to a previous state of your installation.
What's a profile? A profile contains properties defining the “environment” such as operating system, windowing system, architecture and install location. It also contains the list of IUs and the properties associated with each IUs. Artifacts are the actual content being installed (bytes). Metadata consists of Installable units (IUs) that describes the content that can be installed. Profiles are held by a profile registry which can store many profiles.
I tried to revert to a previous build. Error- Cannot find bundles in repository. Hmm, it appeared that p2 had garbage collected the old bundles in my install and was looking in my defined repositories for the bundles. Ironically, I had recently cleaned up our integration builds repo so that we weren't consuming so much space on the eclipse.org servers. So the bundles I needed to revert to were nowhere to be found.
I didn't really want to roll back to an even earlier build. And I wanted to be able to update to newer integration builds. (My eclipse install dates to March 2009 and I've been updating it since then without an issue). Since I'm the Eclipse project release engineer, my solution was to rerun the missing build locally and recreate those exact same bundles on my local linux server. Reproducible builds are essential. We tag the builder and map files each build so that the builds can be run again and create the same binary bits. I wrote a little shell script to use the versions of the map files and builder that were use to create that build. Ran the build. Added the temporary repo to my install and tried to revert again. I was feeling pretty confident that this would work, or to paraphrase xckd, "Watch out, I know release engineering".
No. Could not revert. It turns out that I had also been using an integration build of Mylyn which had also been cleaned from their repo. So I had to revert to an earlier Eclipse milestone build before I had installed Mylyn, then update to the latest SDK I-build and re-install Mylyn.
- You can selectively update part of your install, but cannot selectively revert. Reverting to a profile state is an all or nothing deal.
- Regular expressions are better than release engineers.
OSGi semantic versioning
Eclipse Version Numbering
p2 garbage collection