Continuous Integration, Test, and Deployment of an OpenERP-based Project - LinuxTag 2013

Resources / ERP Odoo

104 views
0 Likes
0 0
Michael Götz-Schneider describes in his talk how Continuous Integration and Continuous Deployment was implemented for a medium-sized enterprise.
As only about 50-60% of the required features are expected to be provided by OpenERP out-of-thebox, the implementation project has been set up using agile software development. Programming teams of three companies are working together using central infrastructure based on Bazaar, Linux, Apache, Redmine, Jenkins, Vagrant and other open source solutions.

Share on Social Networks

Share Link

Use permanent link to share in social media

Share with a friend

Please login to send this presentation by email!

Embed in your website

Select page to start with

6. OpenERP - 6 - elego Software Solutions GmbH - © 2013 Test and Coverage Results

8. OpenERP - 8 - elego Software Solutions GmbH - © 2013 Staging (RELOG)

9. OpenERP - 9 - elego Software Solutions GmbH - © 2013 Staging : Actions for the Release Engineer

10. OpenERP - 10 - elego Software Solutions GmbH - © 2013 Production

11. OpenERP - 11 - elego Software Solutions GmbH - © 2013 Production : Actions for the Release Engineer

12. OpenERP - 12 - elego Software Solutions GmbH - © 2013 Release Notes

15. OpenERP - 15 - elego Software Solutions GmbH - © 2013 Thank you for your attention ! Questions?

5. OpenERP - 5 - elego Software Solutions GmbH - © 2013 Integration ( ILOG )

1. 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

3. OpenERP - 3 - elego Software Solutions GmbH - © 2013 KjellbergERP DevOps

7. OpenERP - 7 - elego Software Solutions GmbH - © 2013 Change Sets Concept

13. 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

2. 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

14. 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

4. 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

Views

  • 104 Total Views
  • 80 Website Views
  • 24 Embedded Views

Actions

  • 0 Social Shares
  • 0 Likes
  • 0 Dislikes
  • 0 Comments

Share count

  • 0 Facebook
  • 0 Twitter
  • 0 LinkedIn
  • 0 Google+