Code authentication in a git repository
Embodiments implement a central commit registry to ensure integrity of code within a Git repository, and the authentication of that code with the requirements of a particular computing system. The git repository stores snapshots of the software code as git commits while a version repository stores git commit files that contain information to uniquely identify git commits that originated from the source system. The git commit files are created with a version repository user that is only shared between a version repository, a source system and a target system. Before the target system deploys git commits received from the git repository, the target system authenticates the git commit by remotely logging into the version repository as a version repository user, querying the version repository for a git commit file that corresponds to the git commit, and verifying that the contents of the git commit file uniquely identifies the git commit.
1 . A method comprising:
receiving, by a target system, a code commit from a git repository, the code commit configured to store software code changes and a unique ID that uniquely identifies the code commit;
remotely logging into a version repository;
querying, by the target system, the version repository to locate a commit file associated with the code commit;
remotely logging out of the version repository;
in response to the query not locating the commit file in the version repository, rejecting the code commit in the target system;
in response to the query locating the commit file in the version repository:
authenticating the code commit; and
processing, by the target system, the code commit in response to the authentication.
2 . The method as in claim 1 , wherein authenticating the code commit includes determining the commit file contains the unique ID.
3 . The method as in claim 1 , wherein processing the code commit includes updating software on the target system with software code changes stored within the code commit.
4 . The method as in claim 1 wherein an administrator creates a version repository user in the version repository and shares credentials of the version repository user with the target system and a source system.
5 . The method as in claim 4 wherein remotely logging into the version repository includes providing the credentials of the version repository user stored in the target system.
6 . The method as in claim 4 further comprising:
receiving, by the source system, a request to commit the software code changes;
generating, by the source system, the code commit based on the software code changes;
transmitting, by the source system, the code commit to the git repository;
remotely logging into the version repository with the credentials as the version repository user;
generating the commit file in the version repository, the commit file containing the unique ID associated with the code commit; and
remotely logging out of the version repository.
7 . The method as in claim 6 , wherein transmitting the code commit to the git repository comprises transmitting the code commit to a git-enabled change and transport system (gCTS), wherein the gCTS routes the code commit to the git repository.
8 . The method as in claim 1 , wherein the git repository is configured to store a plurality of code commits, wherein each code commit is associated with a modification to the software code.
9 . A non-transitory computer readable storage medium embodying a computer program for performing a method, said method comprising:
receiving, by a target system, a code commit from a git repository, the code commit configured to store software code changes and a unique ID that uniquely identifies the code commit;
remotely logging into a version repository;
querying, by the target system, the version repository to locate a commit file associated with the code commit;
remotely logging out of the version repository;
in response to the query not locating the commit file in the version repository, rejecting the code commit in the target system;
in response to the query locating the commit file in the version repository:
authenticating the code commit; and
processing, by the target system, the code commit in response to the authentication.
10 . The non-transitory computer readable storage medium as in claim 9 wherein authenticating the code commit includes determining the commit file contains the unique ID.
11 . The non-transitory computer readable storage medium as in claim 9 wherein processing the code commit includes updating software on the target system with software code changes stored within the code commit.
12 . The non-transitory computer readable storage medium as in claim 9 wherein an administrator creates a version repository user in the version repository and shares credentials of the version repository user with the target system and a source system.
13 . The non-transitory computer readable storage medium as in claim 12 wherein remotely logging into the version repository includes providing the credentials of the version repository user stored in the target system.
14 . The non-transitory computer readable storage medium as in claim 12 further comprising:
receiving, by the source system, a request to commit the software code changes;
generating, by the source system, the code commit based on the software code changes;
transmitting, by the source system, the code commit to the git repository;
remotely logging into the version repository with the credentials as the version repository user;
generating the commit file in the version repository, the commit file containing the unique ID associated with the code commit; and
remotely logging out of the version repository.
15 . The non-transitory computer readable storage medium as in claim 14 , wherein transmitting the code commit to the git repository comprises transmitting the code commit to a git-enabled change and transport system (gCTS), wherein the gCTS routes the code commit to the git repository.
16 . A computer system comprising:
one or more processors;
a software program, executable on said computer system, the software program configured to cause an in-memory database engine of an in-memory database to:
receive, by a target system, a code commit from a git repository, the code commit configured to store software code changes and a unique ID that uniquely identifies the code commit;
remotely log into a version repository;
query, by the target system, the version repository to locate a commit file associated with the code commit;
remotely log out of the version repository;
in response to the query not locating the commit file in the version repository, rejecting the code commit in the target system;
in response to the query locating the commit file in the version repository:
authenticate the code commit; and
process, by the target system, the code commit in response to the authentication.
17 . The computer system as in claim 16 wherein an administrator creates a version repository user in the version repository and shares credentials of the version repository user with the target system and a source system.
18 . The computer system as in claim 17 , further comprising:
receiving, by the source system, a request to commit the software code changes;
generating, by the source system, the code commit based on the software code changes;
transmitting, by the source system, the code commit to the git repository;
remotely logging into the version repository with the credentials as the version repository user;
generating the commit file in the version repository, the commit file containing the unique ID associated with the code commit; and
remotely logging out of the version repository.
19 . The computer system as in claim 18 wherein transmitting the code commit to the git repository comprises transmitting the code commit to a git-enabled change and transport system (gCTS), wherein the gCTS routes the code commit to the git repository.