Cannot override CI_CONFIG_PATH in pipelines

Summary

When trying to override the CI_CONFIG_PATH environment variable in the "Variables" fields (eg, when running a pipeline manually) to specify an other config file than .gitlab-ci.yml, the path is not overriden, and the pipeline loads the configuration from .gitlab-ci.yml. It no .gitlab-ci.yml exists, then auto-devops is used.

Steps to reproduce

  1. Create a gitlab valid config file somewhere in your repository. Name it with anything else than .gitlab-ci.yml (eg: test.yml)
  2. In your project, go to CI/CD > Pipelines > Run Pipeline
  3. In "Variables", create the variable CI_CONFIG_PATH with the value of the file created earlier (eg: test.yml)
  4. (Optionnal) Set CI_DEBUG_TRACE at true
  5. Run the pipeline

Example Project

https://gitlab.com/vmignot/ci_config_path_override

What is the current bug behavior?

The pipeline will use .gitlab-ci.yml if present, and launch auto-devops otherwise.

What is the expected correct behavior?

Gitlab-ci should read the config path from CI_CONFIG_PATH and load it. In our example, test.yml

Relevant logs and/or screenshots

https://gitlab.com/vmignot/ci_config_path_override/-/jobs/193991464

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:		
Current User:	git
Using RVM:	no
Ruby Version:	2.5.3p105
Gem Version:	2.7.6
Bundler Version:1.16.6
Rake Version:	12.3.2
Redis Version:	3.2.12
Git Version:	2.18.1
Sidekiq Version:5.2.5
Go Version:	unknown

GitLab information
Version:	11.9.6
Revision:	14bac95
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	postgresql
URL:		https://xxxxxxxxxxx
HTTP Clone URL:	https://xxxxxxxxxxx/some-group/some-project.git
SSH Clone URL:	git@xxxxxxxxxxxxx:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers:


GitLab Shell
Version:	8.7.1
Repository storage paths:
  • default: /var/git/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 8.7.1 ? ... OK (8.7.1)
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 Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab App ...


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: ...
4/1 ... yes
13/2 ... yes
7/3 ... yes
7/4 ... yes
7/5 ... yes
4/6 ... yes
4/7 ... yes
7/8 ... yes
4/9 ... yes
13/12 ... yes
13/13 ... yes
13/15 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.3)
Git version >= 2.18.0 ? ... yes (2.18.1)
Git user has default SSH configuration? ... yes
Active users: ... 18


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes