Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Platform-releng/Unstable build

< Platform-releng
Revision as of 04:41, 29 November 2016 by Sravankumarl.in.ibm.com (Talk | contribs) (Initial draft)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Purpose

This page is to describe why a build is marked as Unstable

Platform Build

There are two typed of platform builds performed in regular release cycle. The build process is described here Platform-releng/Platform_Build

  • Integration builds(I-Builds) built daily at 8:00 PM EST
  • Maintenance builds(M-builds) built at 4:00 AM on every Wednesday EST

Mark Unstable

Sometimes there is a possibility of

  • Bad commit causing some important test failures
  • Some times due to comparator errors new code might not be in the build.
  • any other problem

In these cases the problem affects only a particular component not every one, so it is not correct to fail a build. If other components are waiting for a particular bug fix they can still test their bug fix. but it is not usable to the end user or regular development.

In this scenario we will mark a build unstable and remove it from the update composite repository so that unstable build is not available during the update. If a particular user still wants to try an update he can still do it using the build-specific repository listed in the download.

If a user wants to mark a build unstable they need to send a mail to platform-releng-dev@eclipse.org mailing list informing the need to do so. Platform-releng team will do the needful

Back to the top