Pipeline editor shows wrong pipeline status immediately after committing the config
Summary
When I commit a config, it tells me that a pipeline wasn't created due to the current config, but then after a few seconds it starts showing the pipeline status. This status used to only show up when you have rules under which a pipeline won't run on the current branch commit.
Steps to reproduce
Head to CI/CD > pipeline editor and commit any configuration (even the default "getting started" template). The initial status will be shown as "no pipeline was created..." and after a few seconds the true status will show up.
Example Project
What is the current bug behavior?
When I commit a config, it tells me that a pipeline wasn't created due to the current config, but then after a few seconds it starts showing the pipeline status. This status used to only show up when you have rules under which a pipeline won't run on the current branch commit.
What is the expected correct behavior?
We should show the status loading state until we can fetch the correct pipeline status.
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)(we will only investigate if the tests are passing)