vester | Easily validate and remediate your vSphere configuration | Command Line Interface library

There are lots of different tasks you can run individually. For instance:

• gradle classes: Will compile your "main" code.
• gradle testClasses: Will compile your "main" code as well as test code.
• gradle jar: Will compile your "main" code and make an executable of it.

None of the above will run your unit tests. On the other hand, the build task depends on all of the above, as well as the test task and more.

In general, if you like to run a particular set of tasks, you do that by defining a new task and then make dependencies to those other tasks you like to run with it. You tried that already, but instead of build you should have used something like compileJava or classes whatever other tasks you need. But always check if there isn't one already that satisfies your needs, like there are in this case. You can read about what tasks are available in Java projects in the documentation for the Gradle java plugin.

Puppet 32 bit client was installed on my 64 bit Windows 2016 Server. The files were actually getting created, but instead of

c:/windows/system32/config/systemprofile/.ssh

the files were created inside

c:/windows/syswow64/config/systemprofile/.ssh

folder by my puppet client.

The %windir%\System32 directory is reserved for 64-bit applications on 64-bit Windows. Most DLL file names were not changed when 64-bit versions of the DLLs were created, so 32-bit versions of the DLLs are stored in a different directory. WOW64 hides this difference by using a file system redirector.

In most cases, whenever a 32-bit application attempts to access %windir%\System32, %windir%\lastgood\system32, or `%windir%\regedit.exe, the access is redirected to an architecture-specific path.

It's weird since, even though files are created in c:/windows/syswow64/config/systemprofile/.ssh folder, the puppet logs in the event viewer were showing that files were being successfully created inside the c:/windows/system32/config/systemprofile/.ssh. This happened because puppet 32 bit clients are unaware of the secret redirection in windows.

The fix for me was to just remove the 32 bit puppet client and install back the 64 bit puppet client since one of my puppet-modules(puppetlabs/vsrepo) was trying to access the knownhost file from c:/windows/system32/config/systemprofile/.ssh folder as it was using 64 bit git.exe client in background.

More about the WOW64 secret redirection in Microsoft documentation here

Solved the issue through adaption of my selection string. In this case it is important to use the {} form (mentioned also here)

In addition I had to announce the aliased column names. The new selection string looks like this: