Single-tenant release tracking

Fleet Release Parity

Every production deployment Azure DevOps recorded in the last 120 days, for the applications that ship one image to more than one customer environment.

Applications
23
In the release cycle
63
Up to date
3
Behind general
24
On their own build
6
In soak now
9
Ready to promote
11

Read from Azure DevOps release records on 27 October 2026 at 11:08. 289 deployments. 2 releases rolled back, 83 replaced before finishing soak. Nothing here is read from a cluster.

Where each environment stands

One row per application, one column per customer environment. Compared against what that application's general environment is running.

Up to date Behind Own build Can't compare No recent deployment Never deployed to ! an attempt did not land this application does not deploy to that customer
Application Africa BDF Colpal Colpal Global Enterprise Gulf HCCB Haldiram MT Mars Modmart SLMG UB
DailyExpensegeneral: no release on record Up to date20260813.1
DailyExpenseFallBackgeneral: no release on record Never deployed to-
DailyExpenseTimeTriggeredgeneral: no release on record No recent deployment!-
FA_External_API_Processor_Prodgeneral: no release on record Never deployed to- Never deployed to- Never deployed to- 3 behind!20251029.1 Never deployed to-
File_Uploader_Prodgeneral: no release on record Never deployed to- No recent deployment!- No recent deployment!- No recent deployment!- Never deployed to- No recent deployment!-
GTAPPAPI-K8s-Managegeneral: no release on record 22 behind!20260710.3 Own build20260902.2 18 behind20260915.2 8 behind20261014.2 2 behind20261021.2 Own build20261026.1 Own build20261023.1 1 behind20261026.2 Own build20261022.1 1 behind20261026.2 14 behind20261005.1
GoogleApiDistanceCalculation_Processorgeneral: no release on record 3 behind20260407.1 3 behind20260407.1 Up to date20260914.2
LiveProcessor-K8s-Managegeneral: no release on record 7 behind20260825.1 No recent deployment!- 8 behind20260812.1
Release - FA Dashboard ACR - Maingeneral: no release on record 4 behind20261026.5 Never deployed to- Never deployed to- No recent deployment!- 21 behind20261012.3 Own build20261026.4
Reporting_Prod_Flexible_TargetAchievementgeneral: no release on recordno general stage No recent deployment20260123.1 No recent deployment20260410.1
Reporting_Prod_Webjob_DSRgeneral: no release on recordno general stage Never deployed to- Colpal DSR-No recent deployment DSR20260810.4No recent deployment DSR20260916.2No recent deployment Gulf DSR-No recent deployment DSR-No recent deployment Haldiram DSR-No recent deployment Never deployed to- Never deployed to-
Reporting_Prod_Webjob_Flexiblegeneral: no release on recordno general stage Never deployed to- Colpal Flexible-No recent deployment Flexible20260701.2No recent deployment Flexible20260916.2No recent deployment Gulf Flexible-No recent deployment Flexible20260701.2No recent deployment Haldiram Flexible20261026.2No recent deployment Never deployed to- Never deployed to-
Reporting_Prod_Webjob_V4general: no release on recordno general stage Never deployed to- Colpal v4-No recent deployment V420260701.2No recent deployment Gulf v4-No recent deployment V420260916.2No recent deployment Haldiram v420261026.1No recent deployment V420260708.1No recent deployment Never deployed to- No recent deployment20261022.2
ShareOrderOnEmailgeneral: no release on record Up to date190003
manager-app-api-prodgeneral: no release on record Never deployed to- Never deployed to- Never deployed to-
mastergeneral: no release on record 3 behind20261026.4 Never deployed to- Never deployed to- 5 behind20261022.5 Own build20261023.1 No recent deployment!-
missing-daystarts-queue-processor-productiongeneral: no release on record Can't compare20260526.1general's records only start at 20260827.1
mt-webjobs(QueueTriggered)-prodgeneral: no release on recordno general stage App APi Processor20260604.1No recent deployment MT v4 Reports20260914.1No recent deployment Modmart Campaign Processor20260902.1No recent deployment Modmart Report Processor20260604.1No recent deployment
mt-webjobs(TimeTriggered)-prodgeneral: no release on recordno general stage Duplicate Sync20260702.1No recent deployment vispera cron job20251001.1No recent deployment Modmart Campaign CronJob20260624.1No recent deployment Modmart Missing DayStart Processor20260702.1No recent deployment Modmart StockEdit Cronjob20251001.1No recent deployment
prodgeneral: no release on record 3 behind20261026.2 10 behind20261005.1 3 behind20261026.2 10 behind20261005.1 3 behind20261026.2 Never deployed to- SLMG20261026.23 behind SLMG -No recent deployment
reporting-api-prodgeneral: no release on record Analytics/Dashboard Reporting20260618.1Can't comparegeneral's records only start at 20260811.2 GT Reporting20260806.2Can't comparegeneral's records only start at 20260811.2 4 behind20260924.1 Analytics Reporting20260609.2Can't comparegeneral's records only start at 20260811.2 Dashboard Reporting20260609.2Can't comparegeneral's records only start at 20260811.2 Can't compare20251031.1general's records only start at 20260811.2 Analytics/Dashboard Reporting20260622.1Can't comparegeneral's records only start at 20260811.2 GT Reporting20260629.2Can't comparegeneral's records only start at 20260811.2
reportprocessor-productiongeneral: no release on record Never deployed to- 14 behind20260602.1 Never deployed to- Never deployed to- Never deployed to- Never deployed to-
target-achievement-api-prodgeneral: no release on record Haldiram target-achievement-api20260630.1Can't comparegeneral's records only start at 20260812.1 haldiram-target achievement webjob-No recent deployment

Why 9 deployment targets cannot be compared (6 cells above)

To say whether a customer is behind or on a build of its own, we have to know whether general ever released the version it is running. Where the customer is on something older than general's earliest record, there is no way to tell - and guessing would mean either reverting somebody's fix or leaving a customer stale. So these are reported as unknown, and the automation holds.

ApplicationCustomerRunningGeneral's records start atGap we cannot see
missing-daystarts-queue-processor-productionColpal20260526.120260827.13 months of general history missing
reporting-api-prodColpal / Analytics/Dashboard Reporting20260618.120260811.22 months of general history missing
reporting-api-prodColpal / GT Reporting20260806.220260811.25 days of general history missing
reporting-api-prodGulf / Analytics Reporting20260609.220260811.22 months of general history missing
reporting-api-prodGulf / Dashboard Reporting20260609.220260811.22 months of general history missing
reporting-api-prodHCCB20251031.120260811.29 months of general history missing
reporting-api-prodHaldiram / Analytics/Dashboard Reporting20260622.120260811.22 months of general history missing
reporting-api-prodHaldiram / GT Reporting20260629.220260811.243 days of general history missing
target-achievement-api-prodHaldiram / Haldiram target-achievement-api20260630.120260812.143 days of general history missing

This clears itself over time. Azure DevOps holds no older records - a 2000-day query returns the same answer - so the missing history cannot be recovered. But once collection runs on a schedule and stores what it reads, every release from then on is on record permanently, and each of these resolves the next time that customer is updated to a version we have seen.