15
OpenERP - 1 - elego Software Solutions GmbH - © 2013 Continuous Integration, Test, and Deployment of an OpenERP-based Project Michael Götz-Schneider elego Software Solutions GmbH - © 2013

Continuous Integration, Test, and Deployment of an OpenERP-based

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 1 - elego Software Solutions GmbH - © 2013

Continuous Integration, Test, and Deployment of an

OpenERP-based Project

Michael Götz-Schneider

elego Software Solutions GmbH - © 2013

Page 2: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 2 - elego Software Solutions GmbH - © 2013

Project Setup

• Kjellberg Foundation/Finsterwalde Client

• OpenERP Extensible ERP System

• elego/Berlin Project Management, Software Architecture, Requirement Analysis

• elego/Berlin (3)

• RCS/Massen (3)

• Kjellberg DL/Finsterwalde (2)

Developers

Page 3: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 3 - elego Software Solutions GmbH - © 2013

KjellbergERP DevOps

Page 4: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 4 - elego Software Solutions GmbH - © 2013

Developers Work and Integration

Developer

• Checks out a version of OpenERP 7.0

• Code the addon and test

• Commit and push the addon

to the repository

CI Server

• Detects the new or changed feature branch

• Merges the changes into a workspace copy of the integration branch

• Runs regression tests

• Merges the feature branch into the integration branch, unless a regression is detected

Page 5: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 5 - elego Software Solutions GmbH - © 2013

Integration (ILOG)

Page 6: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 6 - elego Software Solutions GmbH - © 2013

Test and Coverage Results

Page 7: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 7 - elego Software Solutions GmbH - © 2013

Change Sets Concept

Page 8: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 8 - elego Software Solutions GmbH - © 2013

Staging (RELOG)

Page 9: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 9 - elego Software Solutions GmbH - © 2013

Staging: Actions for the Release Engineer

Page 10: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 10 - elego Software Solutions GmbH - © 2013

Production

Page 11: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 11 - elego Software Solutions GmbH - © 2013

Production: Actions for the Release Engineer

Page 12: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 12 - elego Software Solutions GmbH - © 2013

Release Notes

Page 13: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 13 - elego Software Solutions GmbH - © 2013

Traceability

• Mail notifications are sent to developers to inform about integration

results

• Change sets reference issues (tickets) in commit messages, in the

integration log (ILOG), in the release engineering log (RELOG), in the

release notes

• Change sets have a release label

• Release versions are tagged and committed

• Each module has a version number

• OpenERP offers a module/version menu

Page 14: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 14 - elego Software Solutions GmbH - © 2013

Open Issues and Problems

•Many changes from the OpenERP 7.0 code base

•How to separate the incoming changes

•Conflict resolution is not fully implemented

•Test coverage has to be increased

•Automatic GUI test

•More IT integration tests for LDAP, Email, Webshop …

•Bazaar: traceability and redmine integration is insufficient

Page 15: Continuous Integration, Test, and Deployment of an OpenERP-based

OpenERP - 15 - elego Software Solutions GmbH - © 2013

Thank you for your attention!

Questions?