puppet-lint | Check that your Puppet manifests conform to the style guide | Code Analyzer library

You shouldn't need to clone each repository manually and use local hooks in the way you're doing -- if you have clone access during build time you should be able to do the normal installation approach

To ensure all of the hooks are pre-installed, you'll want to run pre-commit install-hooks as one of the commands in your dockerfile

This will ensure that all of the hook executables are properly cached in your image and then will be available later when you run pre-commit run ...

disclaimer: I'm the author of pre-commit

You can do it with help of systems such as Rake. Rake is sophisticated test runner written in Ruby and is a standard way of running test.

You can see example of Rake files when you generate new Puppet module with puppet module generate companyname-modulename command. In root directory of your project you will find Rakefile where you will see default configuration. In default configuration you can see that validation task is already done and ready to use. Just make sure that paths are ok.

To run validation task you need to make sure that gems mentionded in Gemfile are installed. You can do it with bundle install. To run validation task just run bundle exec rake validate.

So, after further research, I found that the problem was not related to my code, files or configuration but with a problem with Rubygems.

Bottomline, I had to follow this link and manually update the certificate.

It looks like ruby wasn't able to connect to the server to check for dependencies of the gems I was requiring.