Git server implemented in ABAP

via abapGit

by activating the ServiceName ZABAPGITSERVER in transaction SICF

to use it via the web frontend by running transaction ZABAPGITSERVER (or right click on the SICF service ZABAPGITSERVER and choose Test Service)

abapGitServer supports merge requests between two branches of the same repo.

After creating a new branch, push it directly to abapGitServer before committing any changes:

git branch <new>
git push origin <new>

After this operation you can make your changes and commit them to the new branch. When you push a new branch with new commits, the operation will fail.

2018-02-25: Support for tags added, use conversion program ZAGS_MIGRATION_03 to convert old repositories

2018-01-21: Field ADLER32 added in database table ZAGS_OBJECTS, use conversion program ZAGS_MIGRATION_02 to convert old repositories

2018-01-13: Make sure you have the latest development version of abapGit installed

2017-03-12: Key field REPO added in database table ZAGS_OBJECTS, use conversion program ZAGS_MIGRATION_01 to convert old repositories

• https://github.com/larshp/ABAP-Swagger
• https://github.com/larshp/abapGit (the full repository version >= 1.102.0 is needed, not only the latest build on https://raw.githubusercontent.com/abapGit/build/master/zabapgit.abap)

• https://github.com/bunysae/abap_db_preparator

see https://github.com/larshp/ABAP-Swagger

• Web interface: browse/create repository
• No tags, no submodules, no blame
• Primarily tested with abapGit as client

• Automatic backup of objects
• Increased visibility over changes in system

Works with 'git pull' from command line, so all objects can be exported to a different git server if needed, guide

abapGit is your git client and the abapGitServer our server. We first have to setup the ssl connection with the root certificate of the sap system the abapGitServer is running on. After that the abapGitServer can be used like every other git server.

See wiki