This project is read-only.

Starting deployment too fast

Mar 22, 2012 at 9:04 PM


First of all, great tool. I love it :-)

I am setting the build quality, in case the Build does not fail and is the nightly build, automatically in AfterEndToEndIteration using

      Quality="$(QualityOnSucceeded)" />

that works good, it triggers TFSDeployer. But too fast, the Build is InProgess and the deployment is not executed therefore. A few seconds later the build is completed - but already too late for TFSDeployer :-(

Snip from log:

    MachineName=SPS2010TEST01, MappingComputer=SPS2010TEST01
    BuildOldStatus=, BuildNewStatus=Deploy Testumgebung
    MappingOrigQuality=*, MappingNewQuality=Deploy Testumgebung
    UserIsPermitted=True, EventCausedBy=SOLVION\tfsbuildservice
    BuildStatus=InProgress, MappingStatus=
TfsDeployer.exe Information: 0 : 22.03.2012 20:30:36: Eval results:
    isComputerMatch=True, isOldValueMatch=True, isNewValueMatch=True, isUserPermitted=True, isBuildStatusMatch=False

any hints how to cope with that issue? or how to set the build quality later, after the build is completed? or trigger the build ignoring the quality any time it succeeds from a certain user?

thank you very much, bye, stefan


Mar 27, 2012 at 11:35 AM
Edited Mar 27, 2012 at 11:35 AM

update: discussion connected with