GitLab-CI include directive cannot be used on Enterprise Trial

Summary

Gitlab-CI include yaml directive cannot be used while on Enterprise Trial.

Steps to reproduce

  1. Start a Gitlab Enterprise trial on a self-hosted server
  2. Go to the CI Lint page (https://mygitlab.example.com/ci/lint)
  3. Paste the following contents into the Content field and click Validate
include: https://gitlab.com/demo-clusters/include/raw/master/demo-cluster.gitlab-ci.yml

build:
  script:
  - echo foo

Example Project

See above example .gitlab-ci.yml

What is the current bug behavior?

Status: syntax is incorrect
Error: Your license does not allow to use 'include' keyword in CI/CD configuration file

What is the expected correct behavior?

Status: syntax is correct

And a valid table of the jobs described by your manifest.

(What you should see instead)

Relevant logs and/or screenshots

ci-lint-failing-include

See above for example of failing .gitlab-ci.yml

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
$ sudo gitlab-rake gitlab:env:info

System information
System:         Debian 9.4
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.5.5-ee
Revision:       8435f3a
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.6
URL:            https://gitlab.cphy.com
HTTP Clone URL: https://gitlab.cphy.com/some-group/some-project.git
SSH Clone URL:  git@gitlab.cphy.com:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: google_oauth2


GitLab Shell
Version:        6.0.3
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 
$ sudo gitlab-rake gitlab:check SANITIZE=true                                                                                                                                                                                                               
Checking GitLab Shell ...

GitLab Shell version >= 6.0.3 ? ... OK (6.0.3)
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 ... ok
4/3 ... ok
6/4 ... ok
6/5 ... ok
6/6 ... ok
6/7 ... ok
6/8 ... ok
6/9 ... ok
4/10 ... ok
6/11 ... ok
4/12 ... ok
4/13 ... ok
4/14 ... ok
4/15 ... ok
4/16 ... ok
6/17 ... ok
6/19 ... ok
6/20 ... ok
6/21 ... ok
6/22 ... ok
6/23 ... ok
6/24 ... ok
6/25 ... ok
6/26 ... ok
6/27 ... ok
6/28 ... ok
6/29 ... ok
6/30 ... ok
6/31 ... ok
6/32 ... ok
6/33 ... ok
6/34 ... ok
6/35 ... ok
6/36 ... ok
6/37 ... ok
6/38 ... ok
6/39 ... ok
6/40 ... ok
6/41 ... ok
6/42 ... ok
6/43 ... ok
6/44 ... ok
6/45 ... ok
6/46 ... ok
4/47 ... ok
4/48 ... ok
6/51 ... ok
2/52 ... ok
5/53 ... ok
10/55 ... ok
5/56 ... ok
5/57 ... ok
5/58 ... ok
5/59 ... ok
2/60 ... ok
10/61 ... ok
2/62 ... repository is empty
11/63 ... ok
12/64 ... ok
4/65 ... ok
4/66 ... ok
2/67 ... ok
2/68 ... 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 ...


LDAP is disabled in config/gitlab.yml


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
4/3 ... yes
6/4 ... yes
6/5 ... yes
6/6 ... yes
6/7 ... yes
6/8 ... yes
6/9 ... yes
4/10 ... yes
6/11 ... yes
4/12 ... yes
4/13 ... yes
4/14 ... yes
4/15 ... yes
4/16 ... yes
6/17 ... yes
6/19 ... yes
6/20 ... yes
6/21 ... yes
6/22 ... yes
6/23 ... yes
6/24 ... yes
6/25 ... yes
6/26 ... yes
6/27 ... yes
6/28 ... yes
6/29 ... yes
6/30 ... yes
6/31 ... yes
6/32 ... yes
6/33 ... yes
6/34 ... yes
6/35 ... yes
6/36 ... yes
6/37 ... yes
6/38 ... yes
6/39 ... yes
6/40 ... yes
6/41 ... yes
6/42 ... yes
6/43 ... yes
6/44 ... yes
6/45 ... yes
6/46 ... yes
4/47 ... yes
4/48 ... yes
6/51 ... yes
2/52 ... yes
5/53 ... yes
10/55 ... yes
5/56 ... yes
5/57 ... yes
5/58 ... yes
5/59 ... yes
2/60 ... yes
10/61 ... yes
2/62 ... yes
11/63 ... yes
12/64 ... yes
4/65 ... yes
4/66 ... yes
2/67 ... yes
2/68 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.3.6)
Git version >= 2.9.5 ? ... yes (2.14.3)
Git user has default SSH configuration? ... yes
Active users: ... 5
Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)


Checking GitLab ... Finished

Possible fixes