Hello, SAP community! 👋

We’re always on a mission to keep our Sustainable SaaS Sample Application scenario up-to-the-minute. Therefore, we’re eager to share 🎉 the latest enhancement to our sample use-case related to our exceptional Kyma Runtime (kyma-project.io) – the Kyma Runtime Pipeline (click here) in SAP Continuous Integration and Delivery (click here). Feels like early Christmas 🎄🎁

CAP + Kyma + CI/CD = 😍 🥰 ❤️

Our fantastic engineering teams (you guys rock 🎸🤘) have worked hard to provide another crucial component to improve your SAP BTP end-to-end developer experience! Check out Discovery Center (click here) to learn more about the service offering in general and the availability in your preferred SAP BTP region.

This new feature of our beloved SAP CI/CD service offering, supports SAP’s recommended Cloud Native Buildpack (https://buildpacks.io/) approach to craft your Container Images when deploying CAP applications to the SAP BTP, Kyma Runtime! Pretty impressive, right? 🚀 Let’s break it down from the top so you’re fully up to speed with this remarkable pipeline – available for free validation using our SAP BTP, Free Tier or Trial plans!

Kyma + CAP + CI/CD

The SAP Cloud Application Programming Model (CAP) (cap.cloud.sap) sets the gold standard 🏆 for future SAP BTP developer generations, offering a clear set of recommendations, guardrails and best-practices for creating solutions on the SAP Business Technology Platform. When you’re using SAP’s managed Kubernetes offering Kyma, SAP’s guidance includes the use of Cloud Native Buildpacks (click here) to build the necessary Container Images. Paired with paketo (paketo.io), developers can create standardized and reliable Container Images without the hassle of writing and maintaining separate Dockerfiles.

SAP’s Project Piper (project-piper.io) – the advanced CI/CD stuff 😀 – has been supporting the required cnbBuild step (click here) for a while now, and the SAP Continuous Integration and Delivery Service has just launched a new pipeline 🎁, custom-made for application developers in the SAP BTP, Kyma Runtime context. This new Kyma Runtime Pipeline (click here) supports the complete process of building Container Images using Cloud Native Buildpacks, pushing them to your chosen Container Registry like DockerHub, Google Artifact Registry or even your own Container Registry, and an industry-standard Helm-based (helm.sh) deployment to your Kyma Cluster. This will greatly simplify your life as a DevOps engineer, as you can now concentrate on tackling the more intricate DevOps scenarios. 🚀 Meanwhile, SAP’s managed CI/CD offering running on SAP BTP, will take care of handling the majority of your SAP BTP developments or extensions. 🎉 No more complex Jenkins setups required for each and every new development project.

From SAP Business Application Studio to GitHub to SAP CI/CD to SAP Kyma

As always, you can choose a code-based configuration (click here) of your pipeline or use the Job Editor (click here) to set up your job. You’ll find a wealth of configuration options related to the Cloud Native Buildpack approach, and you can continue using the familiar stages that encompass steps like Unit Tests, Acceptance, or Compliance requirements. Be sure to explore the latest documentation 📚 (click here) to learn all about this new pipeline before giving it a go in your own SAP BTP landscape. For the Free Tier and Trial plan users amongst you – please be aware that your Jobs are deactivated after remaining unchanged for one week, but you can easily switch them on again.

For a practical example, we’ve included a simple end-to-end pipeline configuration (click here) in our popular Sustainable SaaS GitHub repository. As the new pipeline and its features might seem overwhelming initially, we’ve also prepared a step-by-step guide (click here) 🗺️ to ensure a smooth setup experience. The sample pipeline (click here) might not cover all available steps (e.g., Unit Tests or wdi5 Tests), but it’s a great starting point for setting up all relevant credentials, like the kubeconfig details of a required service account (click here) or your container registry authentication (click here) details. Once you’ve got the sample scenario up and running, adding additional testing or deployment steps should be a breeze! 🌬️

Now, you might be thinking 🤔, “This sounds like a great achievement, but what if I need my own Dockerfile instead of using Cloud Native Buildpacks?” No worries there – the Container-Based Applications pipeline (click here) is still available and can be used to build regular Container Images based on Dockerfiles.

For the K8s (Kubernetes) enthusiasts in our community who’ve been following the recent SAP Blog Posts in the DevOps context, you’ve likely caught the great update on GitOps with Argo CD & Kyma (click here). Using Argo CD (argo-cd.readthedocs.io) to manage Helm installations in one or more Kyma clusters can be a game-changer. The best part? Consider combining Argo CD with the SAP Continuous Integration and Delivery Service, using the new Kyma Runtime Pipeline to build, test, and finally distribute your Container Images to your Kyma Cluster(s)!

That’s all for now, folks! Please give it a try in your own landscape, and reach out for any question or in case you face any issue!

Happy DevOps deep diving! 🏊‍♂️👩‍💻👨‍💻

Martin