1. Introduction

This article explains CI/CD with different toolchains and importantly different use cases - covering deployments, configurations, and assets propagation across different environments in webMethods.io API gateway.

2. What is CI/CD? 

1196×269 54.4 KB

• Continuous Integration - Every change is validated automatically
• Continuous Delivery - Every promotion is automated to higher stages 
• Continuous Deployment - Every promotion (including configuration changes) to production is automated

For more details on CI/CD please go through https://techcommunity.softwareag.com/techniques-blog/-/blogs/continuous-integration-using-webmethods

3. Pre-Requisites

• Azure DevOps
• NPM

4. CI/CD with API Gateway

1051×621 74.5 KB

4.1 Push asset to Azure DevOps Repository

Login to source API gateway and click on API’s and select the API’s you want to export and say Export ...

1907×596 78.1 KB

Check-in exported API to Azure DevOps repository by clicking on Repos and Upload files.

1900×572 54.2 KB

Click Browse-> select the exported zip file and select the branch as master and commit.

1902×933 85.2 KB

4.2 Pull assets from the repository

Azure DevOps repo is very likely to be private. Unless you have a public repo, you should provide the credentials to access the repository.

If you do not have one or don’t remember the credentials, go to your Azure Repos and select the Clone option. Select Generate Credentials

1549×252 14.9 KB

Copy the URL, username, and password.

602×618 23.7 KB

Configure the Jenkins pipeline job to check out from Azure DevOps repository.

1171×635 24.1 KB

4.3    Deploy to Target Environment

Checkout the cicd-cli developed for API gateway by running the following command. (local workspace)

npm i apigw-cicd-cli

Open the config.json file and update the target environment details:

Export the API’s in target environment by using the below Jenkins pipeline job.

1281×696 22.8 KB

Once the job finishes successfully, you can see the API’s in the target environment.