Skip to content
This repository has been archived by the owner on May 15, 2018. It is now read-only.

building with Jenkins #99

Closed
BladeFireLight opened this issue Dec 22, 2014 · 2 comments
Closed

building with Jenkins #99

BladeFireLight opened this issue Dec 22, 2014 · 2 comments

Comments

@BladeFireLight
Copy link

attempting to build with Jenkins I get this error.

VERBOSE:
Get-DscResource : The term 'Get-DscResource' is not recognized as the name of
a cmdlet, function, script file, or operable program. Check the spelling of
the name, or if a path was included, verify that the path is correct and try
again.
At C:\Program Files
(x86)\WindowsPowerShell\Modules\dscbuild\Test-DscResourceIsValid.ps1:11 char:33

  •             $AllResources = Get-DscResource | Where-Object 
    
    {$_.ImplementedAs ...
  •                             ~~~~~~~~~~~~~~~
    
    • CategoryInfo : ObjectNotFound: (Get-DscResource:String) [], Com
      mandNotFoundException
    • FullyQualifiedErrorId : CommandNotFoundException
@vors
Copy link

vors commented Dec 22, 2014

Currently DSC supported only in x64 PowerShell, so x86 PowerShell doesn't have DSC-specific cmdlets, like Get-DscResource.

@dlwyatt
Copy link
Member

dlwyatt commented Dec 23, 2014

As @vors mentioned, this isn't a problem with the tooling modules. Jenkins just needs to be running the 64-bit version of PowerShell in order to work. I believe there are sometimes a couple of quirks with having a 32-bit process launch 64-bit PowerShell (which the chef client also runs into), such as still resolving some file and registry paths to the 32-bit locations, but at least it allows you to use DSC.

@dlwyatt dlwyatt closed this as completed Dec 23, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants