I expected the onceover tests to run using the suggested method in documentation:
`docker run --rm -v $(pwd):/repo puppet/puppet-dev-tools:latest \
/bin/bash -c "bundle install && bundle exec onceover run spec --force --trace --parallel"
With an expected output similar to:
Steps to reproduce the behavior:
Run the following docker command:
docker run --rm -u puppetdev -v ~/Projects/control-repo:/repo puppet/puppet-dev-tools:4.x /bin/bash -c "gem install bundler:2.2.29 && bundle install && bundle exec onceover run spec"
This results in the following output:
Environment
Version: puppet-dev-tools:4.x
Platform: MacOS (Big Sur 11.6),Docker (20.10.7)
Additional Context
I found this issue while trying to run a onceover job on Puppet CD4PE (4.9.1-Beta) in a Docker container
Describe the Bug
There seems to be an issue running onceover within the puppet-dev-tools container. The classes being tested cannot be found.
Also described here: https://github.com/dylanratcliffe/onceover/issues/317
Expected Behavior
I expected the onceover tests to run using the suggested method in documentation: `docker run --rm -v $(pwd):/repo puppet/puppet-dev-tools:latest \ /bin/bash -c "bundle install && bundle exec onceover run spec --force --trace --parallel"
With an expected output similar to:
Steps to reproduce the behavior:
Run the following docker command:
docker run --rm -u puppetdev -v ~/Projects/control-repo:/repo puppet/puppet-dev-tools:4.x /bin/bash -c "gem install bundler:2.2.29 && bundle install && bundle exec onceover run spec"This results in the following output:
Environment
Additional Context
I found this issue while trying to run a onceover job on Puppet CD4PE (4.9.1-Beta) in a Docker container