Deploy ACE integrations automatically onto CP4I

Deploy ACE integrations automatically onto CP4I

Jun 22 2020

Now that you have migrated your IIB flows to ACE and decided to modernise your integration solution using Cloud Pak for Integration after reading our previous blog, how do you adapt your existing DevOps Pipeline for CP4I on Openshift?

Here is an example of a multi-stage CI/CD pipeline that allows a developer to make changes to an ACE integration locally on-premises and automatically deploy these changes onto a CP4I OpenShift cluster in the cloud.

The steps involved in a typical DevOps CI/CD pipeline are listed below.

1. Developer updates integration and pushes code into Git or any other source control system;
2. Git code commit triggers an on-premises Jenkins job to build the integration artifacts;
3. On-premises Jenkins job builds, tests, and packages integration artifacts;
4. The integration artifacts are uploaded into an artefact repository (eg. Nexus);
5. The on-premises Jenkins job optionally triggers a Jenkins cloud pipeline. For controlled environments, the Operations team is responsible for triggering the deployment pipeline on the cloud;
6. Jenkins cloud pipeline retrieves the integration artifacts;
7. Jenkins cloud pipeline builds a Docker image containing integration artifacts;
8. Jenkins cloud pipeline populates a Helm chart and includes Docker image;
9. The integration is deployed into CP4I.

Need more information?

• IBM Cloud Pak for Integration website