Overview
Each product stores and delivers the build artifacts used in a release differently. This document brings a focal point to all of them and will link out to other supporting documents as necessary.
AlarmBiller
The artifacts for AlarmBiller are a NUGET package that gets uploaded to Octopus and two database backup files used for schema comparison/update. These are the output from an Azure DevOps build pipeline that get uploaded through an Azure DevOps release pipeline.
Development process for creating these artifacts
Manitou
The artifacts for Manitou is an entire directory structure that adds a new folder for each release patch. Also included/updated are "package" folders that contain files for artifacts that are not typically versioned in sync with the rest of Manitou.
These are stored on a file share and are built up by hand in QA with the help of some Azure build and release pipelines.
\\boldfiles\Release\Manitou\Release 2.1.0
Pre-release (Alpha, Beta, etc) are stored in a similar file share location
\\boldfiles\Pre-Release\Manitou\Pre-Release 2.1.0-RC
SedonaOffice
The artifact for SedonaOffice is an installer executable. It is produced from an Azure DevOps build pipeline and a handbuild from an Installer program. These are stored in?
SedonaCloud
The artifacts for SedonaCloud are a NUGET package that gets uploaded to Octopus. This is the output from an Azure DevOps build pipeline that get uploaded through an Azure DevOps release pipeline.
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.
