I think I found a bug in Casper Remote when passing script parameters. I'm using the
BashExample.sh script here. Here is how to recreate the bug:
- Launch Casper Remote and login to JSS
- Select Computers -> any machine
- Goto Scripts -> Select BashExample.sh
- Fill in "parameter 1" with value of "paramA"
- Important: Without selecting anything else and leaving focus on the "parameter 1" field click the "Go" or just enter.
View the log when script is done running and notice that "parameter 1" does not have any value:
[..........]
Custom Parameter 1:
Custom Parameter 2:
Custom Parameter 3:
[........]
Now do the same steps as above setting "parameter 1" to "paramA" and "parameter 2" to "paramB".
Again, leave the focus on the "parameter 2" field and submit the job. You will see something like
this in your log:
[..........]
Custom Parameter 1: paramA
Custom Parameter 2:
Custom Parameter 3:
[........]
So this time you get the correct "parameter 1" value but "parameter 2" is blank. I previously
thought that Casper Remote was just lopping off the last passed parameter but some more testing
proved me wrong.
Now I believe Casper Remote is only updating it's job payload/details as there are changes (or
"un-focus" events) in the UI, and not as values are entered. This bug probably doesn't affect too
many people because I could find no one else having it, but it's annoying. Oddly enough, if you
save the job and run the .casper file you get the results you would expect.
I have tested this on a handful of different machines and I get the same results. Can someone else
out there confirm this bug using the above steps?
Casper version : 6.01
Jim Greenaway
Lindamood-Bell Learning Processes
