stable

Clone or download

Read-only

Cache git commit details in db

Reading git commit details via GitPHP is not really nice for performances. We now store those information in the database, only the first user encountering a cross reference will have a slow response (in case of many commit references to the artifact). Part of story #17180: take into account gitlab commits Change-Id: Ic651fe084ec2b9fdc74fb557e5a0c56dbb265ad6

Modified Files

Name
M plugins/git/db/install.sql +12 −0 Go to diff View file
A plugins/git/db/mysql/updates/2021/202101041133_create_commit_details_cache_table.php +54 −0 Go to diff View file
M plugins/git/db/uninstall.sql +1 −0 Go to diff View file
A plugins/git/include/Git/Reference/CommitDetails.php +113 −0 Go to diff View file
A plugins/git/include/Git/Reference/CommitDetailsCacheDao.php +84 −0 Go to diff View file
A plugins/git/include/Git/Reference/CommitDetailsRetriever.php +111 −0 Go to diff View file
M plugins/git/include/Git/Reference/CrossReferenceGitEnhancer.php +30 −49 Go to diff View file
M plugins/git/include/gitPlugin.php +4 −5 Go to diff View file
A plugins/git/tests/unit/Git/Reference/CommitDetailsRetrieverTest.php +136 −0 Go to diff View file
M plugins/git/tests/unit/Git/Reference/CrossReferenceGitEnhancerTest.php +83 −139 Go to diff View file