-
- Downloads
Assume that unspecified CI config is undefined
We assume that when someone adds a key for the configuration entry, but does not provide a valid value, which causes entry to be `nil`, then entry should be considered as the undefined one. We also assume this is semantically correct, this is also backwards compatible with legacy CI config processor. See issue #18775 for more details.
Showing
- lib/gitlab/ci/config/node/configurable.rb 0 additions, 1 deletionlib/gitlab/ci/config/node/configurable.rb
- lib/gitlab/ci/config/node/factory.rb 11 additions, 7 deletionslib/gitlab/ci/config/node/factory.rb
- lib/gitlab/ci/config/node/variables.rb 1 addition, 5 deletionslib/gitlab/ci/config/node/variables.rb
- spec/lib/ci/gitlab_ci_yaml_processor_spec.rb 4 additions, 4 deletionsspec/lib/ci/gitlab_ci_yaml_processor_spec.rb
- spec/lib/gitlab/ci/config/node/factory_spec.rb 2 additions, 3 deletionsspec/lib/gitlab/ci/config/node/factory_spec.rb
- spec/lib/gitlab/ci/config/node/global_spec.rb 93 additions, 52 deletionsspec/lib/gitlab/ci/config/node/global_spec.rb
- spec/lib/gitlab/ci/config/node/services_spec.rb 1 addition, 3 deletionsspec/lib/gitlab/ci/config/node/services_spec.rb
- spec/lib/gitlab/ci/config/node/variables_spec.rb 0 additions, 19 deletionsspec/lib/gitlab/ci/config/node/variables_spec.rb
Please register or sign in to comment