motiko / force-deploy-with-xml-report-task Goto Github PK

>What steps will reproduce the problem?

Run ant task with DeployWithXmlReportTask

Eg:

<path id="antlib">
    <fileset dir="${ant.library.dir}"/>
</path>

<target name="deployAndTestAndReport">
    <taskdef
        name="sfdeploy"
        classname="com.claimvantage.force.ant.DeployWithXmlReportTask"
        classpathref="antlib"
        />

    <delete dir="test-report-xml" quiet="true"/>
    <sfdeploy
        username="${sf.username}"
        password="${sf.password}"
        serverurl="${sf.server}"
        deployRoot="src"
        runalltests="true"
        junitreportdir="test-report-xml"
        />
</target>

Tests are run with results shown in console output as with standard <sf:deploy>.

>What is the expected output? What do you see instead?

Expect to see junit report in the directory indicated by the 'junitreportdir' 
parameter.

Instead no reports are produced.

I'd also expect to see some additional 

>What version of the product are you using? On what operating system?

ant-deploy-with-xml-report-task-1.4.jar

>Please provide any additional information below.

Using Winter '14 Org. (with ant_salesforce_32.0.zip)
Ant version 1.9.4
OS: Windows 7

What steps will reproduce the problem?
Running CI builds on Bamboo, I suddenly stopped getting test output. Nothing in 
any of the environments, codebases, or setups have changed since last night 
(when it was running properly)

What is the expected output? What do you see instead?
No output

Environment:
Running from a linux box with ant 1.9, connecting to various orgs all running 
SF Winter 15

Please provide any additional information below.
I'm using the old version of salesforce-ant.jar provided here.
I experienced a similar issue last week (suddenly stopped producing output 
overnight), where the solution was to explicitly create the output directory 
and file before calling sfdeploy, but apparently that is no longer sufficient.