win32_process

[nik180]

I am using a similar function to the vbld_findprocess vbscript. I capture the process commandline instead of the process id. I am noticing that some processes have a long path as follows.
"J:\VisBuildPro7\VisBuildCmd.exe" Env=Dev1WAS App=UniformsCorrespondence.ear HudsonConnect=051910084722724 /b J:\promotion\bin\Deploy.bld

These long process commandlines show up as a blank or null. The commandline property works fine for processes with a shorter commandline. Is there some way to capture all commandlines regardless of size. I appreciate any input.
Nik

[kinook]

That works ok in our tests. Testing w/ VBP 7.5b on Win7 x64, the attached project called like so:

"c:\Program Files (x86)\VisBuildPro7\VisBuildCmd.exe" Env=Dev1WAS App=UniformsCorrespondence.ear HudsonConnect=051910084722724 ABC=abcdefghijklmnopqrstuvwxyz0123456789 /b c:\temp\promotion\bin\cmdline.bld

Had the expected output of:

"c:\Program Files (x86)\VisBuildPro7\VisBuildCmd.exe" Env=Dev1WAS App=UniformsCorrespondence.ear HudsonConnect=051910084722724 ABC=abcdefghijklmnopqrstuvwxyz0123456789 /b c:\temp\promotion\bin\cmdline.bld

[nik180]

Thank you. That does work as expected. I wasn't able to replicate this mornings behavior. I will try again tomorrow morning when all our simultaneous builds are running to put it through all the paces. If that works I must have been looking at things wrong. Thanks again.