ERP News

How to implement DevOps for SAP Cloud Platform: 4 best practices

169 0

A successful implementation of DevOps for SAP begins with understanding several best practices. Here are four to get you started.

DevOps-for-SAP

DevOps for SAP

DevOps for SAP-Whether a DevOps implementation is only on the SAP Cloud Platform or is a hybrid approach with the platform as one part, it’s important to know how the unique aspects of the SAP Cloud Platform play into a DevOps strategy.

DevOps aims to make the development process more agile and efficient, while reducing the risks associated with change. It is a set of processes, technologies, and development and operational practices that have been adopted to varying degrees in much of the technology industry. Today, many SAP development teams are starting down the DevOps path, and teams working on the SAP Cloud Platform are no exception.

A DevOps implementation needs to be tailored to the development and operational platforms that admins use. Here are four tips to implement DevOps for SAP Cloud Platform.

1. Break out to shared DevOps toolchain when possible

Use an enterprise-standard Git repository if you have it, rather than SAP Cloud Platform’s Git repository support. The same advice applies to continuous integration tools, such as Drone and Jenkins; Agile management tools, such as Jira and Azure DevOps; and monitoring tools.

For teams that aren’t familiar with the tools used in the rest of the enterprise or for companies that have not adopted this type of DevOps toolchain, it is tempting to just use the SAP Cloud Platform tools. But doing so can have long-term costs in terms of unnecessary lock-in and limited features. For example, the Git repository infrastructure SAP Cloud Platform provides lacks most of the features of GitHub Enterprise, Bitbucket, GitLab and Azure DevOps, and it can also be unnecessarily complex to access from outside of the SAP Cloud Platform environment.

2. Get agnostic about development tooling

When a carpenter goes to a job, they bring their own tools. So, why do we require skilled developers to use enterprise-standard tooling to do the job? Mandatory use of enterprise development tooling has real costs in terms of ramp-up time and accessibility, but they are costs that IT pros have been paying without question for a long time in the SAP world.

Some DevOps tools need to be shared. Version control, ticketing systems and build systems come to mind. However, those tools should have standard interfaces that allow developers to connect using their tools of choice. WebIDE should be the default, but don’t require your developers to use it. Do the work to put infrastructure in place around SAP Cloud Platform to enable developers’ freedom. The good news is if you have already broken out to shared DevOps toolchain as suggested above, then you are nearly there.

Read More Here

Article Credit: TechTarget

Leave A Reply

Your email address will not be published.

*

code