Make PipelineProcessWorker idempotent with until_executed deduplication [RUN ALL RSPEC] [RUN AS-IF-FOSS]
What does this MR do?
Related to #326791 (closed)
The recent comment: #326791 (comment 582144217)
PipelineProcessWorker
is called multiple times in two places;
- In every after_transition of CommitStatuses.
- Every time right after executing the pipeline.
Right now, we are preventing any race conditions via using try_obtain_lease
. However, why not marking the worker deduplicate :until_execing
to prevent before that happens?
This change is behind a feature flag ci_idempotent_pipeline_process_worker
#332963 (closed).
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by Furkan Ayhan