css configuration built tools continuous integration and nightly builds n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CSS Configuration-/ Built- Tools Continuous Integration and Nightly Builds PowerPoint Presentation
Download Presentation
CSS Configuration-/ Built- Tools Continuous Integration and Nightly Builds

Loading in 2 Seconds...

play fullscreen
1 / 10

CSS Configuration-/ Built- Tools Continuous Integration and Nightly Builds - PowerPoint PPT Presentation


  • 85 Views
  • Uploaded on

CSS Configuration-/ Built- Tools Continuous Integration and Nightly Builds. EPICS Collaboration Meeting Aix-en-Provence June 3 rd , 2010 (Jan Hatje) Matthias Clausen - DESY. Configuration- / Built-Tools. Current Situation Continuous Integration Nightly Builds Plans. Current Situation.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'CSS Configuration-/ Built- Tools Continuous Integration and Nightly Builds' - svea


Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
css configuration built tools continuous integration and nightly builds

CSS Configuration-/ Built- ToolsContinuous Integration and Nightly Builds

EPICS Collaboration Meeting Aix-en-Provence

June 3rd , 2010

(Jan Hatje)

Matthias Clausen - DESY

configuration built tools
Configuration- / Built-Tools
  • Current Situation
  • Continuous Integration
  • Nightly Builds
  • Plans
current situation
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
continuous integration
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.
hudson nightly built
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
plans
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