CI Pipelines Can't Run without .gitlab-ci.yml File on Master Branch
Summary
It is not possible to run CI pipelines for a branch with a .gitlab-ci.yml
file without a .gitlab-ci.yml
file on the master branch. This makes it difficult to develop and test a CI configuration before merging into master.
Steps to reproduce
- Create a branch with a
.gitlab-ci.yml
file. - Go to the repository's Pipelines page. It shows “Build with confidence” and a button to “Get start with Pipelines”. It is not possible to run a pipeline for the branch.
What is the current bug behavior?
It is not possible to run any CI pipelines if the master branch of the repository does not have a .gitlab-ci.yml
file.
What is the expected correct behavior?
It should be possible to run CI pipelines for any branches/tags that have a .gitlab-ci.yml
file.
Relevant logs and/or screenshots
None.
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
System information System: Proxy: no Current User: git Using RVM: no Ruby Version: 2.3.6p384 Gem Version: 2.6.13 Bundler Version:1.13.7 Rake Version: 12.3.0 Redis Version: 3.2.11 Git Version: 2.14.3 Sidekiq Version:5.0.5 Go Version: unknown
GitLab information Version: 10.4.2-ee Revision: 30275e2 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.5 URL: https://gitlab-dev.transzap.com HTTP Clone URL: https://gitlab-dev.transzap.com/some-group/some-project.git SSH Clone URL: ssh://git@gitlab-dev.transzap.com:2222/some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: no
GitLab Shell Version: 5.11.0 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
(Checking GitLab Shell ...
GitLab Shell version >= 5.11.0 ? ... OK (5.11.0) Repo base directory exists? default... yes Repo storage directories are symlinks? default... no Repo paths owned by git:root, or git:git? default... yes Repo paths access is drwxrws---? default... yes hooks directories in repos are links: ... 2/2 ... repository is empty 5/5 ... ok 4/6 ... ok 3/8 ... ok 4/9 ... ok 4/10 ... ok 3/14 ... ok 3/15 ... ok 5/16 ... ok Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: OK gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml Checking LDAP ...
Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) (data removed)
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 2/2 ... yes 5/5 ... yes 4/6 ... yes 3/8 ... yes 4/9 ... yes 4/10 ... yes 3/14 ... yes 3/15 ... yes 5/16 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.3.6) Git version >= 2.7.3 ? ... yes (2.14.3) Git user has default SSH configuration? ... yes Active users: ... 3 Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
Possible fixes
Unknown