I have been trying all week to execute a ddk build for our drivers. I have experimented with different scenarios, all to the same resulting end: no successful build output when executed with prefast.

There seems to be some reason GO cannot execute the following command "prefast /log=.\prefast.xml build -e .".

The build executes using a vcxproj file, which executes the command "ddkbuild -quiet -WIN7WLH -prefast free ."

The ddkbuild is a batch file, which sets up the environment for executing the driver build.

Everything seems to be working fine until it gets to the final build command, which is "prefast /log=.\prefast.xml build -e .".

EXEC : error : The build command 'build' returned status '1'. 

There is no output.

 -- the batch file is tested and working correctly in our current build environment, has been for years

 -- the project file has been executed many times over the years, it has not changed

 -- the commands themselves execute correctly when executed from a command window on the agent machine

 -- if I remove the -prefast argument, the build executes correctly.

At this point I am looking for new ideas or alternative solution.  We really want to be able to run with prefast on.

Hello there,

I have deployed a web application to UAT environment and need to know how to test it.  Is there any way to test web application to see if it working (using NAnt script)?  Some sample of NAnt script would be very helpful.

Thanks,
Hong

I am wanting to retrieve some output from a pipeline without that pipleine triggering a build.

Basically I have a couple of maintenance pipelines configured to setup all the our build machines with the required buildtools.  All these tools are required to exist for all of our builds to properly work, however I do not want to make them dependent pipelines, because I do not want them to trigger any of the downstream pipelines. I am finding I would like to have the sync logs available to other projects for record keeping, so we can recreate the exact machine configuration later, should the need arise. 

Is there a way to identify a dependency but not trigger the downstream pipeline? I see no other way to get the output files I need from these pipelines without making them dependent. Setting fetchMaterials="false" is not an option, as I do need to get the materials from other pipleines and source control.