(+44) 0204 566 5056 office@engagingdata.co.uk
CI/CD Package

The plumbing that makes your life easier and consistent. 

Our CI/CD Package is a solution that utilises WhereScape 3D and RED command-line interface, allowing you to automate your deployment using CI/CD Pipelines entirely.

Our solution also compliments the existing WhereScape version control and will enable you to version your objects and deployments using more widely used version control software such as: GIT.

What is Continuous Integration (CI)?

Continuous Integration is a software development practice where all developers merge code changes in a central repository multiple times a day.  

What is Continuous Delivery (CD)?

Continuous Delivery adds the method of automation of the entire software release process.

What is DevOps?

DevOps is a culture shift or a movement that encourages communication and collaboration to build better quality software more quickly with more reliability.

With CI, each change in code triggers an automates build-and-test sequence for the given project, providing feedback to the developer who made the change.

CD includes infrastructure provisioning and deployment, which may be manual and consist of multiple stages.

What is essential is that all these processes are fully automated, with each run fully logged and visible to the entire team.

Continuous Delivery:

Continuous delivery is an important aspect that allows users to automate the end-to-end pipeline for CI/CD.

We can design and develop using WhereScape at the core these functionalities for Continuous Delivery:  

Automatically deploy code from one environment.

Automatically execute test cases.

Take a course of action for successful and unsuccessful test results.

Update a tracking system (Jira or ServiceNow) to keep track of overall workflow.

Automatically Deploy with Confidence:

In an Agile environment, developers are assigned Jira tickets for their daily activities. 

When the developer creates/updates an application, they update the Jira ticket with relevant details like the domain name, model repository name, application name, and build number. 

Build Process Flow

The development or build manager can review the developer’s changes and approve the changes. Once the status of the Jira ticket is changed, Jenkins can identify this change on Jira and trigger a build. 

In the Jenkins build, we can have scripts to create corresponding files for the application the developer worked on. Jenkins can automatically pull the application name from the Jira ticket.

Deployment Process Flow

When the application is ready to be deployed to RED, a developer can create a deployment request on Jira. The developer can identify the application and the build number to deploy against in the Jira ticket.

The deployment manager can review this request and approve this ticket on Jira. Once the status of Jira is changed to “Approved,” Jenkins can automatically trigger a job to pull the files from version control and deploy the files to RED that the developer gave in the Jira ticket. 

The most significant benefit of a CI/CD pipeline is the automation of releases from the initial testing to deployment.

Additional benefits of our CI/CD Package include:

 Eliminate the need for manual intervention

Deliver results faster

Average Implementation time of 4 weeks

Written in all major code languages

Contact Us:

If you’d like to speak to our team, please give us a call.

We will be in touch as soon as possible.

Office: (+44) 0204 566 5056 

Email: office@engagingdata.co.uk

Keep up to date with everything and follow us: