Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335510 - [releng] Track specific 3.7 IBuilds instead of the I-Build composite
Summary: [releng] Track specific 3.7 IBuilds instead of the I-Build composite
Status: RESOLVED FIXED
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 4.1 M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-26 16:04 EST by Andrew Niefer CLA
Modified: 2011-02-25 14:50 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Niefer CLA 2011-01-26 16:04:48 EST 
Recently versioning problems in the platform (bug 335508, bug 334021) have caused problems for e4 builds.

This is because the build mirrors from the 3.7-I-builds repository, but because of the way the slicing works, we get the latest version of each feature/bundle, which may not actually line up with a specific build whenever versions decrease.


To get around this we would need to mirror from a specific 3.7-I-builds/<child> repository.

We already do something in the e4 build to pick a specific IBuild repo for the 4.1 SDK.  We can do the same thing to choose the specific 3.7 I-build.


Doing this means we will use the same version line-up as the 3.7IBuild we are tracking, even if some of the version numbers go backward.
Comment 1 Andrew Niefer CLA 2011-02-25 14:50:42 EST 
this is done