Skip to main content

Deploy to Production

Overview​

Step-by-step procedure to deploy a new release to the production environment, including both MSIX builds and web deployments.

Prerequisites​

When to Use​

  • Scheduled production release after QA sign-off
  • Approved hotfix deployment
  • Post-merge deployment from main branch

Procedure​

Step 1: Verify Release Readiness​

Purpose: Ensure all changes are approved and merged

  1. Confirm all PRs for this release are merged to main
  2. Verify the GitHub sync action has completed. Run manually if it doesn’t fire automatically
  3. Check that the HP Telvie repository has the latest changes

Verification: Git log on HP Telvie repo shows expected commits

Step 2: Trigger MSIX Build (if Electron changes were made)​

Purpose: Generate new MSIX builds for Windows distribution

note

Skip this step if there are no changes in the electron/ folder or build configuration.

  1. Navigate to HPTV+ Pipeline
  2. Click Run pipeline
  3. Select the appropriate branch and environment. Additionally, generate builds for ITG & STG environments to run any tests with additional logs
  4. Click Run

Verification: Pipeline completes successfully and MSIX is uploaded to SharePoint

Step 3: Update Integrity Configuration​

Purpose: Register new Electron version and checksum in Accedo Control

warning

Skipping this step will cause a "corrupted" error modal when users launch the application.

  1. Get the checksum from the build artifacts
  2. Follow the Integrity documentation to add the new version

Verification: New version appears in Accedo Control integrity settings

Step 4: Trigger Web Deployment (if web changes were made)​

Purpose: Deploy web changes to production

  1. Navigate to the Production pipeline
  2. Click Run pipeline
  3. Confirm the deployment
info

Running each environment’s pipeline in parallel might fail due to Sonar checks’s datetime results. To prevent this, simply run them sequentially.

Verification: Changes are visible on production URL after ~5 minutes

Step 5: Post-Deployment Verification​

Purpose: Confirm the deployment was successful

  • Application loads without errors
  • New version is visible in the app

Post-Procedure Verification​

  • Production application is accessible
  • Key user flows work as expected
  • MSIX installer downloads and installs correctly (if updated)

Rollback Procedure​

  1. Web rollback: Re-run the pipeline with the previous release tag
  2. MSIX rollback:
    • Update Accedo Control to point to previous version
    • Optionally rebuild with previous tag if needed

Troubleshooting​

ProblemPossible CauseSolution
Pipeline failsBuild configuration issueCheck pipeline logs, fix and re-run
"Corrupted" error on app launchMissing integrity configUpdate Accedo Control with correct checksum

Escalation​

  1. Slack Channel: #prj-hp-dev