diff options
author | Rémy Coutable <remy@rymai.me> | 2016-09-15 10:17:28 +0000 |
---|---|---|
committer | Rémy Coutable <remy@rymai.me> | 2016-09-15 10:17:28 +0000 |
commit | e28fbd953009416d7f75bb2faccbc378507b4854 (patch) | |
tree | 513478f52fbf7dc5830e25c8f44eb5ac3f3dd757 /doc/update/7.2-to-7.3.md | |
parent | 4768521a6e9d6d8b9a57398ebb5d03aed5b5ac77 (diff) | |
parent | 50e62b3eb8ab030e123e990d1335f68478cc4a4b (diff) | |
download | gitlab-ce-e28fbd953009416d7f75bb2faccbc378507b4854.tar.gz |
Merge branch 'fix-multiple-pipeline-events' into 'master'
22202-similar-code-found-in-defn-mass-108-in-lib-gitlab-diff-position_tracer-rb-98-lib-gitlab-diff-position_tracer-rb-119
Fix the ordering of transition callbacks
Because pipeline status could be changed for the builds in the next
stages, if we process next stages first, the current build would be
out of synchronized, and would need a reload for that matter.
Alternatively, like what I did in this commit, we could process the
next stages later (by using `after_transition` rather than
`around_transition`), and complete what're doing for the current
build first. This way we don't have to reload because nothing is
out synchronized.
Note that since giving `false` in `after_transition` would halt the
callbacks chain, according to:
https://github.com/state-machines/state_machines-activemodel/blob/v0.4.0/lib/state_machines/integrations/active_model.rb#L426-L429
We'll need to make sure we're not returning false because we don't
intend to interrupt the chain.
This fixes #22010.
After this fix, both pipeline events and build events would only show
up once.
See merge request !6305
Diffstat (limited to 'doc/update/7.2-to-7.3.md')
0 files changed, 0 insertions, 0 deletions