CI config should be invalid if entry key specified but not defined
Summary:
CI config is valid when entry key is specified but not defined
Original issue:
Currently when we specify CI configuration with key and empty value like:
image: ruby:2.2
test:
variables:
script:
- rspec
CI Linter will not yield invalid configuration. This is a problem not only with variables
because our current design of CI YAML processor makes it difficult to check whether value is nil
or just unspecified. This will not be a case with new CI configuration (see https://gitlab.com/gitlab-org/gitlab-ce/issues/15060), so we can improve that after we finish refactoring.
Related issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/18764 Workaround: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4745
Workaround still does not inform that value is not valid, it simply fixed an error described in #18764 (closed).
Should we improve that ? /cc @markpundsack @ayufan