Staging

Staging builds duplicate the production database, and try to load this duplicate with the revisions of the staging branches.

Each time you push a new revision on a staging branch, the build created uses a new copy of the production database. The databases are not re-used between builds of the same branch. This ensures:

• staging builds use databases that are close to what the production looks like, so you do not make your tests with outdated data,

• you can play around as much as you want in the same staging database, and you can then ask for a rebuild when you want to restart with a new copy of the production.

Nevertheless, this means that if you make configuration changes in staging databases and do not apply them in the production, they will not be passed on the next build of the same staging branch.

Development

Development builds create new databases, load the demo data and run the unit tests.

A build will be considered failed and highlighted in red if tests fail during the installation, as they are meant to raise errors if something wrong occurs.

If all tests pass, and there is no error, the build will be considered successful.

According to the list of modules to install and test, a development build can take up to 1 hour to be ready. This is due to the large number of tests set in the default Odoo modules suite.

Thanks & Regards,

​

CandidRoot Solutions Pvt. Ltd.

Mobile: (+91) 8849036209
Email: info@candidroot.com
Skype: live:candidroot
Web: https://www.candidroot.com
Address: 1229-1230, Iconic Shyamal, Near Shyamal Cross Road, Ahmedabad, Gujarat