We have released the new version v5 of the out-of-the-box continuous delivery offering that is part of the SAP S/4HANA Cloud SDK and consists of a ready-made Jenkins server and a complete delivery pipeline.
In this blog post, we will walk you through the highlights of the releases. For a complete overview, visit our release notes for the continuous delivery pipeline. The release notes also include the change log of all our releases so far.
At the end of the article, you will find a set of instructions on how to update to the new version.
The docker image for browser-based tests (
We have moved the Node Security Platform (nsp) check into the local tests stage in order to accelerate the pipeline build. To ensure proper security checks of frontend components, it is no longer possible to skip this step.
The Jenkins dashboard now shows the FindBugs reports.
The artifact deployment stage properly considers the inheritance feature of Maven. For example, if the application module does not specify the value of version element, the value from the parent pom will be used.
By default, Jenkins will start with six executors, instead of four.
You can find further fixes and improvements in the complete release notes.
If you are using the pipeline as offered out-of-the-box and did not specify any specific version, you will automatically use the latest version.
To update the Jenkins image as used by the cx-server script, run the following commands on the server hosting the cx-server:
In this blog post, we will walk you through the highlights of the releases. For a complete overview, visit our release notes for the continuous delivery pipeline. The release notes also include the change log of all our releases so far.
At the end of the article, you will find a set of instructions on how to update to the new version.
Continuous Delivery Pipeline: Release Highlights
The docker image for browser-based tests (
s4sdk/docker-node-browsers) now includes a Java Virtual Machine (JVM), so that you can use Java-based tools such as Selenium during end-to-end tests.We have moved the Node Security Platform (nsp) check into the local tests stage in order to accelerate the pipeline build. To ensure proper security checks of frontend components, it is no longer possible to skip this step.
The Jenkins dashboard now shows the FindBugs reports.
The artifact deployment stage properly considers the inheritance feature of Maven. For example, if the application module does not specify the value of version element, the value from the parent pom will be used.
By default, Jenkins will start with six executors, instead of four.
You can find further fixes and improvements in the complete release notes.
How to Update: Continuous Delivery Pipeline
If you are using the pipeline as offered out-of-the-box and did not specify any specific version, you will automatically use the latest version.
To update the Jenkins image as used by the cx-server script, run the following commands on the server hosting the cx-server:
./cx-server stop
./cx-server remove
./cx-server start- SAP Managed Tags:
