Closed satishrajum closed 8 years ago
Yea, the hooks don't work on windows as they are somewhat OS specific. I have also never tested this on windows. I don't think it would be that difficult to change this to be windows friendly.
As a work around you can do the following:
Or
More info about the templates can be found here: https://github.com/nwops/retrospec-templates
Thanks for the reply. I will check both the options and see which one will work.
On Wed, Feb 24, 2016 at 1:16 PM, Corey Osman notifications@github.com wrote:
As a work around you can do the following:
- fork the templates
- remove all offending code inside the clone and pre hook
- commit your changes to your repo
- clone your repo to your C:/Users/userid/.retrospec/repos/retrospec-puppet-templates dir
- retry
Or
- fork the templates
- remove all offending code inside the clone and pre hook
- commit your changes to your repo
- clone your repo to some other dir
- retrospec puppet --template-dir='new_template_dir'
More info about the templates can be found here: https://github.com/nwops/retrospec-templates
— Reply to this email directly or view it on GitHub https://github.com/nwops/puppet-retrospec/issues/53#issuecomment-188388670 .
Actually, this is something we will need to change in the code. Because of how windows works with scripts and associating them with a executable we can't just call the clone hooks directory like in linux. So we will need to call these hooks with ruby hook_name
instead.
Hooks provided in the gems are not working with the external repos on windows.