1 / 10

Enhancing CSS Configuration Tools: Continuous Integration and Nightly Builds

This document discusses the current state and future plans for Continuous Integration (CI) and Nightly Builds in the CSS project at DESY. It outlines the process of using a central CVS repository where developers commit changes post-debugging, followed by local JUnit tests and compilation. The role of Hudson in regularly checking the repository for changes and managing nightly builds of CSS products is detailed. Additionally, the transition from CVS to Mercurial is addressed, highlighting a new workflow model that ensures efficient code integration and build processes.

svea
Télécharger la présentation

Enhancing CSS Configuration Tools: Continuous Integration and Nightly Builds

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. CSS Configuration-/ Built- ToolsContinuous Integration and Nightly Builds EPICS Collaboration Meeting Aix-en-Provence June 3rd , 2010 (Jan Hatje) Matthias Clausen - DESY

  2. Configuration- / Built-Tools • Current Situation • Continuous Integration • Nightly Builds • Plans

  3. Current Situation • One central cvs repository • Changes get committed to the central repository as soon as the developer has debugged his ‘local’ version • How to find out whether something breaks before other do? • Run the JUnit tests locally • Compile locally • Commit to central repository • Update your local version from central repository • Check again

  4. Continuous Integration • Hudson Process checking the cvs repository on a regular basis for changes • If so check out all the files for the configured project and run JUnit and compile a new Product (full built) • If errors occur • Send e-Mail to the user who committed the code which is breaking now.

  5. Hudson Nightly Built • Nightly built of all CSS products • DESY – CSS version(s) • CSS (DESY) • CSS on an island (DESY agnostic) • All CSS headless products (not all for now) • Copy nightly built products to ftp server

  6. Hudson Overview Page

  7. Hudson CSS Built

  8. Hudson Built Problem view

  9. Hudson Recent Commits

  10. Plans • Moving from cvs to Mercurial • Moving from cvs repository at DESY to Mercurial at SourceForge • New working model: • Get snapshot from central Mercurial repository to local Mercurial repository • Make changes locally commit to local repository • Run Hudson continuous integration test process • Run Hudson nightly built process from local repository • If successful • Commit to central Mercurial repository • Get new snapshot from central repository

More Related