You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2019. It is now read-only.
• Added support to allow users to include/exclude elapsed time results from flow jobs/runs:
• To be performance efficient, instead of dynamically judging whether a job/run is a flow one every time loading the elapsed time report, add a column “FlowRun” in “BuildResultDate” and “BuildResultExtract” tables (as well as any other tables that are necessary) in Azure DB. When that run result entry is stored into Azure DB, that column will be set to “1” if that is a flow run, or “0” otherwise.
• Add a check box on views below to allow users to include/exclude elapsed time results from flow jobs/runs:
• “Total Elapsed Time List of all Projects” view
• “Job Elapsed Time List” view
• “Job Elapsed Time per build” view
The text was updated successfully, but these errors were encountered:
Copied from TFS work item #234599.
• Added support to allow users to include/exclude elapsed time results from flow jobs/runs:
• To be performance efficient, instead of dynamically judging whether a job/run is a flow one every time loading the elapsed time report, add a column “FlowRun” in “BuildResultDate” and “BuildResultExtract” tables (as well as any other tables that are necessary) in Azure DB. When that run result entry is stored into Azure DB, that column will be set to “1” if that is a flow run, or “0” otherwise.
• Add a check box on views below to allow users to include/exclude elapsed time results from flow jobs/runs:
• “Total Elapsed Time List of all Projects” view
• “Job Elapsed Time List” view
• “Job Elapsed Time per build” view
The text was updated successfully, but these errors were encountered: