Re: [cbi-dev] [platform-releng-dev] Does aggregator repo require change

[Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>]

On Thu, Jul 4, 2013 at 9:03 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

Hi all,

I'm cross-posting to platform-releng-dev and cbi-dev because it's still unclear to me what is CBI and what is Platform.
I've made progress in setting up an Hudson job for Platform [0] with the help of Denis and Thanh. Then build failed because of the following issue in eclipse.platform.team [1] which is now resolved [2]. So I retried a build from Hudson hoping this change would allow to go further, however it seems like job still consumes older version of eclipse.platform.team with bug still being there [3]. I tried to clean job workspace and re-run job, but it still gets the older commit.
Does anyone know how to force consumption of this latest commit in aggregation? Does it require change to the aggregator repository? Does it require a magic git option?

If you are building from an aggregator commit (like I20130702-0800), then you need a new commit in the aggregator in order to pick up the fixes, and that'll happen on the next I build.

If you want to pick it up early, you'll have to check out the appropriate branches in the submodules that you want.  In our platform build, we use submodule-checkout [1].  It depends on repositories.txt [2] for which branch belongs to which submodule.


[1] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/production/build-functions.shsource#n429

[2] http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/streams/repositories.txt

--
Paul Webster
Hi floor.  Make me a sammich! - GIR