[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cross-project-issues-dev] Question about Build ID's
- From: "Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>
- Date: Thu, 18 Jun 2009 16:38:42 +0200
- Delivered-to: firstname.lastname@example.org
- Thread-index: AcnwDPepG7EdsjQORQO+gOKI/lWBYgAFUCxg
- Thread-topic: [cross-project-issues-dev] Question about Build ID's
My question was about *caching* and not about *changing* :)
I'm aware that the bucky builder doesn't change anything.
But does it have a cache of old artifacts which it uses
in case the id of an artifact is unchanged (although the
contents may be changed)?
My guess was yes, since I heard rumors of similar p2
caching mechanisms on the eclipse releng-dev mailing
list. Actually this caching was a reason why several
of the Eclipse Platform components had to tag their
artifacts even for null changes, just in order to make
sure p2 metadata is regenerated properly rather than
taking it from a cache.
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
> -----Original Message-----
> From: cross-project-issues-dev-bounces@xxxxxxxxxxx
> [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Thomas Hallgren
> Sent: Donnerstag, 18. Juni 2009 14:04
> To: Cross project issues
> Subject: Re: [cross-project-issues-dev] Question about Build ID's
> Hi Martin,
> The Galileo Builder will not change anything. All contributed
> are supposed to be signed and packed by the respective
> contribution. The
> builder won't even open the files.
> Thomas Hallgren
> Oberhuber, Martin wrote:
> > Hi all,
> > I'm not sure how many other projects do this, but the TM project
> > embeds its build ID's into the feature description text shown in
> > the about dialog (via about.mappings).
> > Now it can happen that a build's contents does not change at all,
> > but the build ID changes; in the TM case, our 3.1 release is the
> > same as our RC4, but the build ID is "3.1" rather than "3.1RC4".
> > I'm wondering how the Galileo Builder treats this. Given that our
> > plugin and feature ID's have not changed, would the Galileo builder
> > take our "old" plugins with the "3.1RC4" build ID embedded from
> > some cache? For some plugins / features, the build ID might even
> > be MUCH older.
> > Or does it fetch fresh data from our update site on every run,
> > thus ensuring that the latest build ID, "3.1" is embedded?
> > The stuff on /releases/galileo which I just checked contains a
> > mixture of "RC3" and "RC4" build ID's. I'm wondering whether there
> > is a chance to rectify this... in my understanding,
> > /releases/galileo and .../staging are the same at the moment,
> > so what about doing a clean build of .../staging when PDT and
> > Teneo are done with their things?
> > Cheers,
> > --
> > Martin Oberhuber, Senior Member of Technical Staff, Wind River
> > Target Management Project Lead, DSDP PMC Member
> > http://www.eclipse.org/dsdp/tm
> > _______________________________________________
> > cross-project-issues-dev mailing list
> > cross-project-issues-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> cross-project-issues-dev mailing list