Stan Hu 2d233dac45 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		2019-03-26 01:04:06 -05:00
..
archive_trace_service_spec.rb
compare_test_reports_service_spec.rb
create_pipeline_service_spec.rb	Add suffix for merge request event	2019-03-01 22:52:38 +09:00
destroy_expired_job_artifacts_service_spec.rb	Remove expired artifacts periodically	2019-01-24 20:50:42 +09:00
destroy_pipeline_service_spec.rb	Clear pipeline status cache after destruction of pipeline	2019-03-26 01:04:06 -05:00
ensure_stage_service_spec.rb
extract_sections_from_build_trace_service_spec.rb
pipeline_trigger_service_spec.rb
play_build_service_spec.rb
prepare_build_service_spec.rb	Create framework for build prerequisites	2019-03-20 12:04:40 +11:00
process_build_service_spec.rb
process_pipeline_service_spec.rb
register_job_service_spec.rb
retry_build_service_spec.rb
retry_pipeline_service_spec.rb
run_scheduled_build_service_spec.rb
stop_environments_service_spec.rb
update_build_queue_service_spec.rb
update_runner_service_spec.rb