Distributed development – and abapGit are still a relatively new concept as part of SAP development, however the potential uses and benefits are clear.



Figure: Potential uses and benefits for abapGit


During 2019, one of Basis Technologies lead developers Marcello Urbani began to look at abapGit and how distributed development could complement our internal software development practices, and for SAP customers using our existing DevOps platform ActiveControl.

Some of the initial journey is detailed in this series of online SAP Blogs:
Link 1
Link 2
Link 3

The key drivers – and perceived benefits – of this project were as follows:

1. To support the adoption of DevOps and CI/CD enabling true on-demand SAP change delivery, and enable faster business and customer response.
2. To enable SAP customers to harmonize and integrate SAP development with cloud and web development processes used in other areas of their technological organisation.
3. To limit the growth of infrastructure costs and demands that would otherwise be probable.

As part of an internal proof of concept within Basis Technologies, an architecture involving ActiveControl integrated with Jenkins, abapGIT and docker containers was envisaged.



Figure: abapGIT based distributed development workflow, with ActiveControl.


The key points of this workflow would be as follows:

(i) Multiple developers / teams work on the same code / objects at the same time using local containerised Development environments.
(ii) These developers commit changes to the central repositories at the appropriate time in the development lifecycle.
(iii) These changes are merged into the Master branch and deploy into SAP Main Development.
(iv) ActiveControl would then be used to deploy to QA and then Production after testing.


Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment