Rationale:
We have been using this plug-in in our heterogeneous infrastructure extensively. We rely on it on used platforms and we need to be informed when there is any where it doesn't work or doesn't have an anticipated effect. Current situation is that it silently doesn't work, can stick, throws an exception etc.

For the reason above I've established a CI job for all available platforms in our infrastructure and verify its functionality. There are several obstacles which I need to resolve for my success.

Some already known obstacles:

• plug-in hard depends on core and JNA
• JNA isn't supported on all our platforms - it is a known fact, but in that case there isn't a proper fall-back mechanism (for ex. see issue JENKINS-29507)
• JNA is unsupported on some more exotic platform combination (for ex. MS Windows on ia64) - Jenkins doesn't address that, but depends on JNA without a fall-back mechanism (it needs deeper investigation)
• even JNA is supported officially on the target platform (for ex. RHEL ppc64), it contains a bug and really doesn't work (for ex. issue JENKINS-15792 - not addressed by JNA yet, not Jenkins-core, 4.2-snapshot works though)
• pre/post build step sticks on MS Windows 2003 server

So the main goal for this JIRA is fixed the plug-in and its testsuite to be able to execute that CI job on almost all our platforms and verify continuously that it works and nothing get broken.

Follow-up work will be broken to small pieces with their own JIRAs - based on the obtained results.