First implementation #2
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Freckle relies on Jenkins for some in-VPC CD activities. We're trying to move to a more managed solution (CodeBuild), but one feature Jenkins still provides is locking of shared resources between independently-triggered builds. For example, to allow only one deployment per environment at a time, and to ensure we never trigger more than one QA at a time (regardless of environment) via Lambdatest. The latter is due to an unfortunate bug somewhere that leads to any queuing at Lambdatest resulting in QA errors.
This action explores an independent distributed locking mechanism built on S3, that we could use when we migrate away from Jenkins. For the public-facing usage and implementation details, see the rendered README.