customtools not working

[moodysma sma]

I'm trying to understand how this plugin works.  I've create a global tool called "Pstools", exported Path is "Pstools".  Install automatically is set to "http://download.sysinternals.com/files/PSTools.zip" and the label is "PsTools", when I create a job I get the following error message, I don't see it doing any extraction or download from the url.

Started by user anonymous
[CustomTools] - PsTools: Starting installation
ERROR: Wrong EXPORTED_PATHS configuration. Can't find \PsTools
Finished: FAILURE

[moodysma sma]

I tried removing the exported paths, but there is no download or extraction of the zip:

This is my batch build cmd:

rem echo %PATH%

echo %PsTools_HOME%

%PsTools_HOME%\PsExec.exe

Output:

Started by user anonymous

[CustomTools] - PsTools: Starting installation

[CustomTools] - PsTools: Tool is installed at C:\Users\user\.jenkins

[CustomTools] - PsTools: Setting PsTools_HOME=C:\Users\user\.jenkins

Building in workspace C:\Users\user\.jenkins\jobs\hello_world4\workspace

[workspace] $ cmd /c call C:\WINDOWS\TEMP\hudson2592194391930325096.bat

C:\Users\user\.jenkins\jobs\hello_world4\workspace>rem echo C:\Users\user\.jenkins;;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v4.0\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\runtime\win64;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\bin;C:\Program Files\MATLAB\R2014a\runtime\win64;C:\Program Files\MATLAB\R2014a\bin;C:\Program Files\MATLAB\R2013b\runtime\win64;C:\Program Files\MATLAB\R2013b\bin;C:\Python27;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files (x86)\NTP\bin;D:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;D:\Program Files\Microsoft SQL Server\120\DTS\Binn\;D:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;D:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;D:\Program Files\Microsoft SQL Server\120\Tools\Binn\;D:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;D:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files (x86)\Microsoft SDKs\Windows Azure\CLI\wbin;C:\Program Files\MATLAB\R2014a\polyspace\bin;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.1\;C:\Program Files (x86)\nodejs\;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\polyspace\bin;C:\Program Files (x86)\QuickTime\QTSystem\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\ProgramData\Oracle\Java\javapath;C:\Program Files\Microsoft HPC Pack 2008 R2\Bin\;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v4.0\bin\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\runtime\win64;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\bin;C:\Program Files\MATLAB\R2014a\runtime\win64;C:\Program Files\MATLAB\R2014a\bin;C:\Program Files\MATLAB\R2013b\runtime\win64;C:\Program Files\MATLAB\R2013b\bin;C:\Python27;C:\Program Files\Java\jdk1.7.0\bin;C:\Program Files (x86)\NTP\bin;D:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;D:\Program Files\Microsoft SQL Server\120\DTS\Binn\;D:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn\;D:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\;D:\Program Files\Microsoft SQL Server\120\Tools\Binn\;D:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio\;D:\Program Files (x86)\Microsoft SQL Server\120\DTS\Binn\;C:\Program Files\Microsoft\Web Platform Installer\;C:\Program Files (x86)\Microsoft ASP.NET\ASP.NET Web Pages\v1.0\;C:\Program Files (x86)\Microsoft SDKs\Windows Azure\CLI\wbin;C:\Program Files\MATLAB\R2014a\polyspace\bin;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.1\;C:\Program Files (x86)\nodejs\;C:\Program Files\TortoiseGit\bin;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\MATLAB\MATLAB Production Server\R2015a\polyspace\bin;C:\Program Files (x86)\QuickTime\QTSystem\;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\; 

C:\Users\user\.jenkins\jobs\hello_world4\workspace>echo C:\Users\user\.jenkins 

C:\Users\user\.jenkins

C:\Users\user\.jenkins\jobs\hello_world4\workspace>C:\Users\user\.jenkins\PsExec.exe

'C:\Users\user\.jenkins\PsExec.exe' is not recognized as an internal or external command,

operable program or batch file.

C:\Users\user\.jenkins\jobs\hello_world4\workspace>exit 9009 

Build step 'Execute Windows batch command' marked build as failure

Finished: FAILURE

[Victor Martinez]

Labels.should match where you run your job. So, if you say your custom tool install a particular software for Linux then when you configure your job you also set those restrict labels field im order to run in a Linux box.

I guess that's the issue

Cheers

[sma]

Yes, sorry a newbie at Jenkins and understanding the terminology now.

> --
> You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/GLkIaLuCtNs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b13a2e97-a570-42d6-891f-8baa58cf1269%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[sma]

Is there a way to deploy the tools on absolute path instead of under the workspace?

I know that tools are supposed to abstract the location, but we have hybrid processes that need to refer to an absolute path as well which id rather not go under the workspace.

> On Aug 27, 2015, at 6:02 PM, Victor Martinez <victormar...@gmail.com> wrote:
>