cloudblog
2018/06/05
June 05, 2018
3 min read

CI/CD for APIs and Backend Implementations

Agile development of production APIs requires their inclusion in the Continuous Integration (CI) / Continuous Deployment (CD) process:
  • Merge the implementation into a shared repository and have it automatically verified,
  • Automated pipeline deploying the changes into multiple environments such as test, staging, pre-production, production.
WSO2 API Cloud is fully automatable via APIs including API export and import, and other configuration aspects. This makes it easy to integrate API Cloud-based gateway into whatever CI/CD platform you are using. Also, in most cases, you would want you CI/CD process for APIs to be a part of the process that you have for API backend implementation. This ensures that these two evolve consistently. While all platforms are different, we have published a reference implementation that uses GitHub as the code repository, Travis as the CI/CD platform, and WSO2 Integration Cloud as the backend hosting platform:

Check it out, adapt to your process, and let us know what you think!