vault backup: 2024-05-17 14:29:17
This commit is contained in:
3 files changed
+78
-14
No files matched your search
@@ -0,0 +1,54 @@
|
||||
---
|
||||
lang: en
|
||||
tags:
|
||||
- HowTo
|
||||
---
|
||||
# Odoo.sh Production Upgrade
|
||||
|
||||
## Prepare
|
||||
|
||||
Disable upgrade mode on `upgrade` branch
|
||||
## Restore
|
||||
|
||||
Create a backup on `main` branch
|
||||
## Upgrade
|
||||
|
||||
Enter upgrade mode on `main` branch.
|
||||
|
||||
Upgrade from Odoo `14.0` to `16.0`.
|
||||
|
||||
Merge `upgrade` branch into `main` branch once database upgrade is done.
|
||||
|
||||
## Configure
|
||||
|
||||
After the upgrade restore execute this steps:
|
||||
|
||||
* Install `sale_order_line_position`
|
||||
* Remove `sale_order_line_pos`
|
||||
* Upgrade `base`
|
||||
|
||||
Activate views (XML-ID, **name**):
|
||||
|
||||
* partner_type_order.partner_type_order, **partner_type_order.view_partner_form**
|
||||
|
||||
Update server actions:
|
||||
|
||||
Update snippets (XML-ID, **name**):
|
||||
|
||||
* studio_customization.odoo_studio_product__cd8b9256-5b26-49cb-a852-49f7836ea517, **Odoo Studio: product.template.product.form customization**
|
||||
|
||||
Remove views ((XML-ID, **name**):
|
||||
|
||||
* **mint_system.mrp_workorder.mrp_workorder_view_form_tablet.remove_button_action_continue**
|
||||
|
||||
Install snippets:
|
||||
|
||||
* account.view_move_form.x_sale_order_id
|
||||
|
||||
New fields:
|
||||
|
||||
* ir_model.account_move_line.x_sale_order_id
|
||||
|
||||
## Verify
|
||||
|
||||
Customer executes test cases.
|
||||
@@ -0,0 +1,22 @@
|
||||
---
|
||||
lang: en
|
||||
tags:
|
||||
- HowTo
|
||||
---
|
||||
# Odoo.sh Test Upgrade
|
||||
|
||||
There is no official documentation on how a Odoo.sh database is upgraded. This note provides an overview:
|
||||
|
||||
* In the Odoo.sh repository create an upgrade branch
|
||||
|
||||
The name of the branch should contain the Odoo version (as there might be multiple upgrade branches)
|
||||
|
||||
* In Odoo.sh project move the branch to the staging section
|
||||
* In the upgrade tab activate the upgrade
|
||||
|
||||
Whenever a commit is done on this branch Odoo.sh will apply the upgrade scripts
|
||||
|
||||
* Add the git submodules to the repository
|
||||
* Once all required Odoo modules are available test with customer
|
||||
* If the feedback loop is closed merge the upgrade branch into the main branch
|
||||
* Execute the upgrade
|
||||
+2
-14
@@ -5,18 +5,6 @@ tags:
|
||||
---
|
||||
# Odoo.sh Upgrade
|
||||
|
||||
There is no official documentation on how a Odoo.sh database is upgraded. This note provides an overview:
|
||||
## [[Odoo.sh Test Upgrade]]
|
||||
|
||||
* In the Odoo.sh repository create an upgrade branch
|
||||
|
||||
The name of the branch should contain the Odoo version (as there might be multiple upgrade branches)
|
||||
|
||||
* In Odoo.sh project move the branch to the staging section
|
||||
* In the upgrade tab activate the upgrade
|
||||
|
||||
Whenever a commit is done on this branch Odoo.sh will apply the upgrade scripts
|
||||
|
||||
* Add the git submodules to the repository
|
||||
* Once all required Odoo modules are available test with customer
|
||||
* If the feedback loop is closed merge the upgrade branch into the main branch
|
||||
* Execute the upgrade
|
||||
## [[Odoo.sh Production Upgrade]]
|
||||
Reference in new issue
Block a user