Iko[N]otE

I will be short on the topic as you too only seeking the resolution to the problem in the title. This tutorial is based on using Vmware Workstation 11 on Windows 8.1 host using an Ubuntu 14.04 guest. Note : you have to have the vmware tools, client additions installed on the quest machine! First go to the Vmware client's terminal when you are ready to shrink it down and type: sudo vmware-toolbox-cmd disk list This will give you the mount points that can be shrinked individually. For me I will only go with shrinking the main disk with "/" (root). First lets wipe the free space clean so the shrinker will know what is free to get rid of: sudo vmware-toolbox-cmd disk wipe / To shrink: sudo vmware-toolbox-cmd disk shrink / That's it, after the process in my case I've had a 4.4G file shrinked down to 1.7G, which is much closer to what the client OS saw (1.5G).

Currently I use Jenkins version 1.6x. For the most curious here is an example XML that shows the structure. For those of the visual types there will be some treats after the code. Ok now, let's see how these tags translate on the report UI. First we are seeing failed results. These are either failures or errors . When looking at the test report main page, we'll see a minimal summary. Let's look at a failed test now, where we also supplied and output (e.g. STDOUT). Let's see how this is put together in code. I have also pointed out the components of the heading. The heading can have another component too: Errors are also failed tests, but you really should add an extra error output to the report for them: And finally the passed code is a plain entry. Still, you may supply a normal output to it via the element. Conclusion The source XSD file I used to figure out how the JUnit XML should look like