Pipeline is not available in UI after creating new project from template
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Summary
After creating a new project using a project template with a .gitlab-ci.yml file, the pipeline as specified in .gitlab-ci.yml is not available in the UI, and navigating to Build > Pipelines shows "There are currently no pipelines." After any commit, the pipeline appears.
Steps to reproduce
- Create new project. Select
Create from template. - Select
Use templatefor any template that includes a.gitlab-ci.ymlfile. - Name project and select visibility level and then select
Create project. - After project has been created, navigate to
Build>Pipelines. - Observe "There are currently no pipelines."
Example Project
https://gitlab.com/knorquist/pipeline_test_pages-plain-html https://gitlab.com/knorquist/pipeline_test_ruby-on-rails
What is the current bug behavior?
No pipelines are available after creating a project from template where a pipeline is specified in .gitlab-ci.yml.
What is the expected correct behavior?
Pipeline should be available and viewable in UI after creating a project from template.
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)
