The Software and Systems Engineering Experts​
The Software and Systems Engineering Experts​
SmarterProcess logo

Contacts

SmarterProcess / ReqPro

ul. Antoniego Pajdaka 5/98
03-134 Warsaw, Poland
NIP : 8921405210
Regon : 146293701

About Products

About us

Ink drawing: a consultant beside a client engineer at two monitors, with a control unit on a test bench behind them
Sketch: a completed checklist with an acceptance seal and a key on a server module

Handed over, ready to run · your team keeps the know-how

Process Consulting

Deployment automation (CI/CD) consulting services

Build, test and release pipelines that ship engineering software faster, with every change traceable.

Overview

Software delivered faster, with every deployment automated and repeatable

We build CI/CD pipelines that build, test and deploy your software from commit to production without manual steps, and with a tested way back. We link the pipeline to IBM Engineering Lifecycle Management, so each release can be traced back to its work item and requirement.

Most teams we meet already build automatically but still release by hand, with scripts that differ per environment and approvals sent by e-mail. We keep the build jobs that work and add one deployment process for every environment, approval gates in the tool and a tested way back.

We work with HCL DevOps Deploy, GitLab, Jenkins and Azure DevOps, for business applications, engineering and embedded software, internal tools and the IBM Engineering Lifecycle Management platform itself. We tailor the tools to how you work, not the other way around.

Everything runs on your own servers, including networks without internet access, and your team keeps the pipeline after handover.

Your release path

One pipeline from commit to production, with a way back

Rollback to the previous version
  1. Commitlinked to a work item
  2. Buildevery change
  3. Automated testson every build
  4. Deploy to testthe same process
  5. Approvala gate in the tool
  6. Productionwith full history
Every stop can leave a trace in IBM Engineering Lifecycle Management

Your starting point

Where does your software delivery stand today?

Three situations we see before most automation projects.

A failed pipeline run
Errors found after the deploymentTests run with every deployment
A manual deployment checklist
Repetitive steps done by handRepeatable and unattended
Environments out of sync
Test differs from productionOne process on every environment

Also a starting point

  • Releases that take too long
  • Built software that customers cannot use yet
  • Specialists busy with repetitive deployment work

Pipeline + IBM Engineering Lifecycle Management

Every build, test run and release leaves a trace in IBM Engineering Lifecycle Management

We connect the pipeline to IBM Engineering Lifecycle Management, so you can follow each requirement to the build, the test results and the release that delivered it.

Build

IBM Engineering Workflow Management

The build result and its change sets appear on the work item.

  • Work item 4127
  • Build 2.8.0 · passed
  • Change sets linked

Tests

IBM Engineering Test Management

Test results are recorded for each build, and a failed test opens a linked defect.

  • Test run on build 2.8.0
  • 46 passed · 1 failed
  • Defect 912 opened and linked

Release

IBM DOORS Next

Each requirement shows the tests that validate it and the release that delivered it.

  • REQ-218 validated by 3 tests
  • Delivered in release 2.8.0
  • Ready for the audit

We use the IBM Engineering Lifecycle Management integrations and REST APIs with Jenkins, GitLab or HCL DevOps Deploy. Auditors in regulated industries get the trace they ask for without a separate report. Example data on the cards.

Talk to an engineer

How we work

From manual releases to automated deployments

We prove the pipeline on one application before we roll it out.

  1. 1

    Audit

    We audit your deployment scripts, projects and teams, agree the goal with an owner, and select the tools for your needs, maturity and budget.

  2. 2

    Pilot

    We automate the full release of one application, from build to production.

  3. 3

    Rollout

    We bring the other applications and environments onto the same pipeline.

  4. 4

    Handover

    We document the pipeline and train your team on the selected tools, so your specialists keep it running.

What we need from you

  • Access to your deployment scripts and environments
  • One application for the pilot
  • The people who release today
  • One owner who makes decisions
Talk to an engineer
Two engineers at a monitor showing a deployment pipeline with every stage passed, from commit to production

What stalls automation, and what we do about it

  • No sponsorWe agree the goal and an owner before the pilot.
  • Old, complex technologyWe start with one application and keep the pilot small.
  • Only one person knows the releaseThat person helps design the pipeline.
  • No time for itWe agree a small scope and set priorities with the owner.
  • No way backRollback is automated and tested before the first production release.

What you get

Faster releases with fewer errors

Automation reduces human error and project risk throughout software production and deployment.

  • Script audit report

    What works, what breaks and what to fix first.

  • A working pipeline

    One application released end to end, unattended.

  • Tested rollback

    A way back to the previous version, tried before you need it.

  • Audit trail

    Approvals, notifications and deployment history in the tool.

  • Documented process

    How to run, change and maintain the pipeline.

  • A trained team

    Training on the tools you selected, for your deployment team.

FAQ

Questions we hear before a deployment automation project

What is the difference between continuous integration, delivery and deployment?

Continuous integration builds and tests every change automatically. Continuous delivery adds automated deployment to test environments, so every build is ready to release and production is one approved step away. Continuous deployment sends every change that passes the tests to production without a manual step. Most teams we work with start with integration and delivery and keep an approval before production.

Do we need a deployment tool if we already have Jenkins or GitLab?

Not always. Jenkins and GitLab CI/CD build and test well. Releasing to many servers and environments, with settings per environment, approvals and rollback, is easier in a deployment tool such as HCL DevOps Deploy. We often use GitLab or Jenkins for the build and HCL DevOps Deploy for the release. If your deployments are simple, GitLab alone can be enough.

Do we still need manual tests?

Yes, for what automation does not check well, such as usability and exploratory testing. We plan manual tests by risk and record their results against the same build, so the release decision uses both.

What happens when a deployment fails?

The pipeline deploys versioned packages, so it can return to the previous version with the same process. We test the rollback before the first production release.

Where do we start, and what do you need from us?

With an audit of your deployment scripts and a pilot on one application. We need access to the scripts and environments, the people who release today and one owner who makes decisions.

Can you work with the deployment scripts we already have?

Yes. We audit and evaluate your current deployment scripts and optimize them. Scripts that work become steps in the new pipeline.

Do you work on premises and in regulated environments?

Yes. We install and run the tools on your own servers, including networks without internet access, so approvals and deployment history stay inside your network.

Can we see who deployed what, and when?

Yes. Every deployment has a history of who deployed which version, where and when, with approvals and notifications.

Can automated tests run as part of each deployment?

Yes. Automated tests run on every deployment, and their results decide whether the pipeline continues.

Newsletter

The SmarterProcess newsletter

Tips, product news and webinar invites on IBM software, DOORS and the other vendors’ tools we deliver. One email a month.

Get it in your inbox

Check your inboxWe’ve sent a confirmation link to . Click it to start your subscription. Can’t see it? Check your spam folder.