-
- Downloads
Clear pipeline status cache after destruction of pipeline
`project.pipeline_status.has_status?` is cached, which can lead to Error 500s in the UI if the this condition is used to check whether a pipeline exists for a commit. We now expire the cache to ensure that the information is consistent. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/59453
Showing
- app/services/ci/destroy_pipeline_service.rb 2 additions, 0 deletionsapp/services/ci/destroy_pipeline_service.rb
- changelogs/unreleased/sh-clear-pipeline-status-cache-upon-destroy.yml 5 additions, 0 deletions...nreleased/sh-clear-pipeline-status-cache-upon-destroy.yml
- spec/services/ci/destroy_pipeline_service_spec.rb 13 additions, 2 deletionsspec/services/ci/destroy_pipeline_service_spec.rb
Loading
Please register or sign in to comment