Keep around commits only on pipeline create
What does this MR do?
Since the pipeline SHA doesn't change, we don't need to update keep arounds every save.
Why was this MR needed?
This is minimal change to fix this: https://gitlab.com/gitlab-org/gitlab-ce/issues/23503
Merge request reports
Activity
Milestone changed to %8.13
Reassigned to @rymai
Enabled an automatic merge when the build for 67b96255 succeeds
@ayufan Please don't forget the ~"Pick into Stable" next time! ;)
@grzesiek Merge when succeeds didn't happen
Mentioned in commit 6d709417
@ayufan This is very likely that this is related by recent problem on gitlab.com. We need to solve our performance problems to be able to tell. I will of course look into the code again.
Mentioned in merge request gitlab-com/www-gitlab-com!3412 (merged)
Mentioned in commit 88adf6c5
Please register or sign in to reply