1 / 20

Polarsys

Polarsys. Release Engineering [Initial & Draft Version]. Release Topics. Roadmap Policies Continuous integration. Release Topics. Roadmap Policies Continuous integration. Polarsys Release. A release is a main value of Polarsys

garima
Télécharger la présentation

Polarsys

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Polarsys Release Engineering [Initial & Draft Version]

  2. Release Topics Roadmap Policies Continuous integration

  3. Release Topics Roadmap Policies Continuous integration

  4. Polarsys Release A release is a main value of Polarsys Objective for OPEES: setting up the Polarsys's release engineering, ensuring the ability to deliver Polarsys platforms Objective for Polarsys: delivering and promoting the first Polarsys platforms

  5. Polarsys Release - Definitions A Polarsys release is a delivered version of the Polarsys platform A Polarsys release is declined in bundles A bundle contains a consistent set of integrated components. Identified first: Operational(for use in operations), Experimental (for use on experiments) In the future: possibility to define new bundles

  6. Polarsys Release - Definitions • Bundles (continuing) • Operational: [Definition –Integration of certified components – To be improved] • Experimental: [Definition –Integration of validated components; some are already certified – To be improved]

  7. Polarsys Release - Definitions A Polarsys release planning defines a release number, date, a set of bundles with the components that they contain

  8. Release Target Target Progressively, all the Polarsys technical domains must be covered

  9. Polarsys Release - Activities Definition of the Polarsys release planning Definition of release number, date, bundles Actors: Steering Committee, Architecture Board, CCB, Release Engineer Definition of the Polarsys release contents Bundles Bundles contents Actors: Release Engineer, Component Leaders, Architecture Board, CCB

  10. 2012's Polarsys Releases [Draft] First Polarsys Releases Initial Releases Engineering Domains, inc. Research Experimental Polarsys platform Operational Polarsys platform Engineering Domains Essential Technical Domains Modeling Polarsys platform Eclipse Polarsys platform Workbench Releases by Iteration January December

  11. 2012's Polarsys Releases #1: Eclipse Polarsys platform Set up of the release infrastructure Initialization of the VLTS specific aspects (virtualization, archiving, etc.)

  12. 2012's Polarsys Releases #1: Eclipse Polarsys platform #2: Modeling Polarsys platform = Eclipse Polarsys platform + Modeling Eclipse components (e.g., MDT Papyrus, Acceleo, EGF) Management of several bundles definitions, builds and publications Synchronization with several Eclipse projects / release train

  13. 2012's Polarsys Releases #1: Eclipse Polarsys platform #2: Modeling Polarsys platform #3: Operational Polarsys platform = Modeling Polarsys platform + non-Eclipse components (Topcased, etc.) Importation of non-Eclipse code into Polarsys (IP review, VCS, etc.) Technical integration (API, etc.)

  14. 2012's Polarsys Releases #1: Eclipse Polarsys platform #2: Modeling Polarsys platform #3: Operational Modeling Polarsys platform #4: Experimental Polarsys platform = Operational Polarsys platform + Non-Eclipse based bundles (gPM, FramaC, UNISIM, etc.) Specific release engineering process (CAML, C, Maven, etc.), non-EPL components

  15. Release Topics Roadmap Policies Continuous integration

  16. Release Policies The Polarsys policies define all the rules that must be respected by the component projects for a successful Polarsys release process Cf. Polarsys Wiki [TBD]

  17. Release Topics Roadmap Policies Continuous integration

  18. Release Trains Eclipse Release Train E.P1 Eclipse CMP Src Build Result Aggre-gation Packa-ging Build E.Pn Polarsys Release Train Polarsys CMP Src Build Result Aggre-gation Build P.P1 Packa-ging (for patched Eclipse or Polarsys Component) P.Pn Patched CMP Src Build Result Aggre-gation Patched Build

  19. Release Engineering - Activities Definition of Component Build Chain Actors: Component Committer Definition of Polarsys Build Chain Actors: Release Engineer Control of Component Build Chain Actors: Component Committer Control of Polarsys Build Chain Actors: Release Engineer

  20. Release Engineering Tooling • Reusing the Eclipse environment • SCM (e.g., Git, SVN) • Tools (e.g., Buckminster, Ant, Tycho) • Job environment (e.g., Hudson), servers • Possibility to use EGF for modeling all the continuation integration steps

More Related