summaryrefslogtreecommitdiff
path: root/doc/update/7.2-to-7.3.md
diff options
context:
space:
mode:
authorRémy Coutable <remy@rymai.me>2016-09-15 10:17:28 +0000
committerRémy Coutable <remy@rymai.me>2016-09-15 10:17:28 +0000
commite28fbd953009416d7f75bb2faccbc378507b4854 (patch)
tree513478f52fbf7dc5830e25c8f44eb5ac3f3dd757 /doc/update/7.2-to-7.3.md
parent4768521a6e9d6d8b9a57398ebb5d03aed5b5ac77 (diff)
parent50e62b3eb8ab030e123e990d1335f68478cc4a4b (diff)
downloadgitlab-ce-e28fbd953009416d7f75bb2faccbc378507b4854.tar.gz
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