Release Management/rPath Management Console Customization
Contents |
Introduction
This document describes the different phases of customizing to rPath Management console of Openbravo ERP Professional Subscription version 2.50 and above.
General process work flow
- Build the packages with customization requested
- Promote to QA branch
- Announce to QA to test
- Promote to release branch
- publish
Perquisite
Packaging machines
As we distribute Openbravo ERP Professional Subscription appliance for 32-bit and 64-bit architecture, packaging are done in both.
Here are the system we use, for login access please contact Release Management
- System for 32-bit : 192.168.102.78 (tde2-32)
- System for 64-bit : 192.168.102.82 (tde2-64)
set the context to point to [on.openbravo.com rBuilder]
Set context on both architectures
edit ~/.conaryrc [ops-2.50] buildLabel oberp.openbravo.com@openbravo:oberp-2.50-devel installLabelPath oberp.openbravo.com@openbravo:oberp-2.50-devel
mkdir ~/ops-2.50 cd ~/ops-2.50 cvc context ops-2.50
Add top-left product logo
cvc co rapa-branding-custom
cd rapa-branding-custom
# copy the product logo here
# edit rapa-branding-custom.recipe
r.addSource('prod-logo.gif', dest='%(datadir)s/raa/content/images/banner-logo.gif')
save and cook the package
rmake build rapa-branding-custom.recipe rmake commit [pid] commit -m " message"
Customize center company logo
Package rapa-branding-custom
cd rapa-branding-custom
r.Symlink('/opt/OpenbravoERP/web/images/CompanyLogo_big.png','%(datadir)s/raa/content/images/CompanyLogo_big.png')
save and cook the package
rmake build rapa-branding-custom.recipe rmake commit [pid] commit -m " message"
Package rapa
This rapa package need to be packaged in architecture 32-bit and 64-bit. first make the changes in any one of the architecture (say 32-bit) cook and commit, then checkout the package in other architecture (64-bit) just build and commit.
cvc co rapa edit menu.patch sections login.kid and master.kid for appropriate section of CustomerLogo_Big.png
Note refer to previous release packages in [on.openbravo.com rBuilder]
rmake build rapa.recipe rmake commit [pid] commit -m " message"
Group update
As all the packages are packaged in appropriate architecture, the group package need to be build
ssh tde2-64 cvc co gropu-ops-appliance cd gropu-ops-appliance cvc cook --allow-flavor-change 'group-ops-appliance[!dom0,domU,!vmware,xen is: x86]' 'group-ops-appliance[!dom0,!domU,!vmware,!xen is: x86]' 'group-ops-appliance[!dom0,!domU,vmware,!xen is: x86]' 'group-ops-appliance[!dom0,domU,!vmware,xen is: x86_64]' 'group-ops-appliance[!dom0,!domU,!vmware,!xen is: x86_64]' 'group-ops-appliance[!dom0,!domU,vmware,!xen is: x86_64]'
Promote devel to qa stage
As the customization are done in the devel label and tested for its look and feel, it has to be promoted to QA stage.
ssh tde2-64 ops-2.50-promote-qa
Announce to QA
Mail to staff dot qa at openbravo dot com and release dot management at openbravo dot com. specifying
- what are the new update made
- where to refer to the update <label from on.openbravo.com>
Promote QA to Release label
On green light from QA the updates can be promoted from QA label to release label.
ssh tde2-64 ops-2.50-promote-release
Publish
Now we have to make this updates available to customers
- Login to ops-2.50-promote-release
- Click on Schedule Outbound Mirroring
- Click on mirror now
- Monitor the logs for successful completion
Announcements
Mail to on-update-announce at openbravo dot com, please refer to the template below
Subject : OBUA-<yyyymm-dd> Professional Appliance 2.50
Body :
Openbravo Update Advisory: <yyyymm-dd>
Release Date: <month dd, year> (eg:July 22, 2009)
Product: Openbravo ERP Professional Subscription Appliance 2.50
Description:
<explain about the update>