Automating CI/CD Across a Connected Building Platform
Ficode replaced manual deployment routines with Jenkins pipelines for a commercial building energy platform. Centrally published libraries, versioned releases and managed service restarts made backend, web and mobile delivery less dependent on individual machines and engineers.
The project in context
The client operates a building energy intelligence platform used to monitor commercial building systems. Releases relied on manual deployment steps and local dependency caches. Ficode introduced Jenkins-based automation and versioned release handling to make the delivery process clearer and more repeatable.
Manual deployments. Inconsistent builds. Difficult recovery.
Software delivery depended too heavily on the person and machine handling each release. Builds could behave differently because shared dependencies came from local caches. Engineers also had to restart services after reboots and reverse releases manually.
The challenge Before
Manual releases
Deployment steps depend on engineersVariable builds
Local caches affect dependency versionsRecovery by hand
Restarts and rollback require manual workWith Ficode Connected Approach
Automate delivery
Jenkins runs defined build and deployment stepsPin dependencies
Shared libraries publish explicit versionsManage releases
Versioned directories, restarts and rollbackMake dependencies consistent. Automate delivery. Keep a route back.
Standardise
Published two shared libraries with explicit versions so service builds no longer depended on local caches.
Automate
Created dedicated build pipelines for services and deployed their artefacts into versioned directories.
Recover
Used system-managed services for restart after reboot or process failure and retained the previous release for rollback.
Extend
Introduced a dedicated pipeline for the Angular web application and separate pipelines for building and releasing the mobile applications.
From source change to a managed, versioned release
Source and libraries
Versioned code and centrally published dependenciesJenkins build
Produces artefacts using explicit library versionsVersioned deployment
Current release runs; previous release retainedCONNECTED OUTCOME
Backend and web releases follow defined Jenkins pipelines and versioned release directories. Services restart under system management, and the previous release remains available for rollback.
Release handling that the team can repeat
Consistent dependencies
Two shared libraries are published centrally with explicit versions, reducing reliance on individual developer-machine caches.
Repeatable service delivery
Dedicated Jenkins build pipelines produce service artefacts that are deployed into identifiable, versioned release directories.
Defined restart and rollback paths
System management handles service restart, while the current/previous release arrangement keeps an earlier version available.
Web and mobile pipelines
The Angular portal has its own deployment pipeline, and mobile applications use separate build and release pipelines.
Confirmed technology and implementation scope
Jenkins; shared libraries; versioned release directories; system-managed service restarts; Angular web and mobile application pipelines.
