On the verge of migrating from v2.4 to 3.3.2 i`am facing some odd behaviour from the Standalone Agent on an IBM z/OS V1.11. I was able to run the Agent under Unix System Services with the jvm parameter -Dos.name=unix. This made the spacecheck in org.apache.commons.io.FileSystemUtils work. With the 3.3.2 Agent i`am getting lots of java.lang.IllegalStateException: Unsupported operating system at org.apache.commons.io.FileSystemUtils.freeSpaceOS(FileSystemUtils.java:200) even with the env. variable set.
The Agent seems to loose or unset the variable while running which is kind of odd.
After some more testing i came to the enlightnment that the issue is a JDK one. Appareantly the IBM JDK overwrites the os.name variable which makes my workaround of setting it manually to something already known by apache.commons.io worthless. Great!
Have to dig in the IBM Docs to investigate a little bit further. Extending apache.commons.io would probably an option.
as a follow up to the suggested Solution (modified apache.commons.ioFileSystemUtils.java)... I`am appareantly not able to modifiy the Agents Classpath (Dir) on the Client side. The Classpath zip with the Agents Classpath`s jar`s gets downloaded from the Bamboo server and modifying the classpath dir`s contents only triggers redownloading on agent restart.
Also working with -cp on the agents startup command does not seem to work at all.
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot