#3
|
|||
|
|||
Quote:
{[1]"}sourceanalyzer{[1]"} -b %someBuildID% {[2]"}%devenv%{[2]"} {[3]"}%solutionToCompile%{[3]"} %anyBuildVariables%where {[x]"} indicate quotes that follow the behavior you outlined and x indicates a set (both must be either present or absent.) I include a quote in the override devenv path, something like this: "sourceanalyzer -b %buildID% "%devenv%hoping for: ""sourceanalyzer -b someBuildID "pathtodevenv\devenv.com" ....but getting: "\"sourceanalyzer -b someBuildID \"pathtodevenv\devenv.com" .... Quote:
%devenv% %solutionToCompile% %anyBuildVariables%as parameters to sourceanalyzer -b %buildID% Quote:
sourceanalyzer -b %buildID% %correctDEVENV%and reset it afterwards. Using this solution I would still need to overcome the quotation issue from above, but would save me a lot of time modifying each step by hand. Also before you sugest using something like "Run Script" let me explain my situation... To give you a idea of the size of the project, using VBP it takes over 14 hours to compile, one of the 2 current versions of this software utilize VB6 and VS2010, the other version uses VS2010, vs2008, VS2005, and VB6 (it is the older version). The older version has over 2000 steps, the newer is segmented across ~40 build files. In addition, we are not the developers, we provide software assurance on these products for the US Govt. Every time the developer drops new software, we provide static code analysis and regression testing on it. They use VBP 7.7a, and every time there is a new drop we get a new set of build files. Thank you for your assistance, James Mathews |
Tags |
hp fortify |
Thread Tools | |
Display Modes | Rate This Thread |
|
|