Overview
Each product deploys a release differently. This document brings a focal point to all of them and will link out to other supporting documents as necessary.
AlarmBiller
Deployment to production is done through Octopus. There are some helper scripts that may need to be run on a case-by-case basis but this is not a regular flow. Deployment can be scheduled and should be done after hours as all dealer databases will be upgraded. Typically this is triggered by development after
Manitou
The Manitou deployment process involves a lot of manual steps. Helper programs were written but most of the time BoldGroup techs are the ones doing the upgrade for our customers.
Manitou 2.1 - Upgrade Requirements (Sign Off)
ManitouNEO - Update Instructions
Manitou 1.6.4 to Manitou 2.0.0 - Upgrade Instructions
Manitou 2.0.0 to Manitou 2.1.0 - Upgrade Instructions
SedonaOffice
The SedonaOffice Installer is run on all target workstations. It will upgrade the database as needed and install the latest files.
SedonaOffice - Server Reinstallation Guide
SedonaOffice - AWS Deployment Documentation
SedonaCloud
The artifacts for SedonaCloud are a NUGET package that gets uploaded to Octopus. This is the output from an Azure DevOps build a pipeline that gets uploaded through an Azure DevOps release pipeline.
SedonaOffice - Octopus Tentacle & SedonaCloud Install
Sedona-X Mobile
There are two artifacts for Sedona-X Mobile. One is an apk file that gets loaded into the Google Play Store. The other is an iOS bundle that gets loaded into Apple App Store.
Once these are pushed into the respective stores and approved, users simply update from their devices in the normal manner.
SIMS
SIMS uses a program called Live Update.
