0914577244
So rspec-puppet 2.4+ has strict variables enabled which causes test failures. The problem is that the puppet modules have never worked with strict_variables = true due to backwards compatibility & import ordering. Since this has not been true, lets disable it in the unit testing for now. Perhaps some day we will be able to turn this back to true. This should allow us to lift the 2.3.x cap that we added as part of https://review.opendev.org/#/c/618854/. Change-Id: Idbf837e87072c829c94e0356b8536088cf98c3bb
23 lines
996 B
YAML
23 lines
996 B
YAML
- hosts: all
|
|
tasks:
|
|
- shell:
|
|
cmd: |
|
|
set -e
|
|
set -x
|
|
if [ "{{ puppet_gem_version }}" != "latest" ]; then
|
|
export PUPPET_GEM_VERSION='~> {{ puppet_gem_version }}'
|
|
fi
|
|
# TODO(tobias-urdin): Remove when we dont pin rspec-puppet
|
|
export RSPEC_PUPPET_VERSION='{{ rspec_puppet_version }}'
|
|
# NOTE(aschultz): rspec-puppet 2.4+ has strict variables enabled
|
|
# which causes test failures. The problem is that the puppet modules
|
|
# have never worked with strict_variables = true due to backwards
|
|
# compatibility & import ordering. Since this has not been true,
|
|
# lets disable it in the unit testing for now. Perhaps some day
|
|
# we will be able to turn this back to true.
|
|
export STRICT_VARIABLES=no
|
|
./run_unit_tests.sh
|
|
executable: /bin/bash
|
|
chdir: '{{ ansible_user_dir }}/workspace'
|
|
environment: '{{ zuul | zuul_legacy_vars }}'
|