SAP From Giving Up to Getting Started Series: abapGit Update and Uninstall

Overview

Let's take updating abapGit as an example. Managing our code through abapGit is actually similar in operation. Updating the independent version is a bit like the original version management method without version management tools. Updating the developer version is closer to the original intention of abapGit.

1. Update

1.1 Standalone version

To update to the latest version, you need to first download the latest independent version of the code to the local folder, download address , and then upload the code in the newly downloaded file zabapgit_standalone.prog.abap to the ZABAPGIT_STANDALONE program through SE38, overwriting the previous code (formerly known as ZABAPGIT_FULL) and activate the program.

1.2 Developer version

Installing the developer version of abapGit (in a separate development package, such as $ABAPGIT) can automatically update the code. How to update depends on the environmental conditions of our system.

1.2.1 Online update

If the system is connected to the Internet, create an online repository for the abapGit package. When an update is available, a "Pull" link will appear in the menu. When you click Pull, the latest version of the code will be downloaded and installed.

1.2.2 Offline update

If the system is not connected to the Internet, you need to create an offline repository first.

To update abapGit, first download the latest developer version file, then select "Import ZIP" in abapGit to import the compressed file.

Click Pull zip

1.3 Frequently Asked Questions about Updated Versions

Updates to abapGit may sometimes cause very serious problems, such as causing some objects to become inactive or even DUMP. If you encounter this kind of problem, please follow these steps:

1. Install and activate the latest standalone version (see above).
2. Run the standalone version to update the abapGit developer version.
3. If the update is not complete, use SE24 to completely delete inactive objects or objects with differences.
4. Restart the standalone version and perform a new "Pull" operation or an "import ZIP" operation.
5. If this doesn't solve the problem, leave feedback on GitHub.

2. Uninstall abapGit

1. Use SE38 or SE80 to delete the ABAP program ZABAPGIT*. If you have changed the program name, delete it according to the name you changed.
2. Delete queue object EZABAPGIT via transaction code SE11
3. Delete transparent table ZABAPGIT via transaction code SE11
4. Deletion of MIME objects ZABAPGIT_CSS_COMMON and ZABAPGIT_JS_COMMON via transaction code SMW0
5. Use transaction code SE24 or SE80 to remove interface ZIF_APACK_MANIFEST (optional, programs cloned from github may still use this interface)