Pessimistic locking implementation using AWS code commit
We want to implement a pessimistic locking of code commit and wanted to find out steps to implement this. Would appreciate if anyone can provide guidance on this.
Could you please elaborate why would you need pessimistic locks for a git-based version control system (AWS CodeCommit is based on git)? What is your requirement? Any specific workflow you want to implement or a business process you want to support? Is there maybe another way for achieving what you want?
As Dmitry asked, CodeCommit is a Git based system and its concurrency handling follows the same logic as other Git systems (such as to use multiple branches to resolve conflicts merges to main branch), please elaborate your use case so we can better assist you with the best tools / technologies.
continuous integration with awsAccepted Answerasked 3 years ago
Does Git-LFS (Large File Storage) have support in Code Commit?asked 2 months ago
Commit has the wrong Authorasked 3 years ago
Redshift stored procs best practice for transactions locking tables and avoiding serialization isolation violationsasked 2 months ago
CodeCommit - notifications for author of PR'sasked 2 months ago
Pessimistic locking implementation using AWS code commitasked 16 days ago
share code commit repositories between aws accountsasked 3 months ago
CodeBuild job triggered by Githab occasionally gets wrong commitasked 2 months ago
Code Commit Branching ErrorAccepted Answerasked 3 years ago
Pass CommitId of a CodeCommit tag to CodeBuild projectasked 3 years ago