8000 Update the Build and Testing Process · Issue #172 · chocolatey/ChocolateyGUI · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Update the Build and Testing Process #172
Closed
@gep13

Description

@gep13

Currently:

  • StyleCop Errors will fail the Build
  • But artifact will not get published
  • Code Analysis Errors will fail the Build
  • But artifact will not get published
  • DupFinder errors will not fail the build
  • Artifact will get published (assuming no StyleCop or Code Analysis errors)
  • InspectCode errors will not fail the build
  • Artifact will get published (assuming no StyleCop or Code Analysis errors)

Need to make it so that:

StyleCop

  • Errors will fail the Build
  • Report is surfaced as an artifact, regardless of build success/failure
  • XSL transform is performed on the report to make it human readable
  • When possible in AppVeyor, or using Test REST API, publish as Test Report

Code Analysis

  • Errors will fail the Build
  • Report is surfaced as an artifact, regardless of build success/failure
  • XSL transform is performed on the report to make it human readable
  • When possible in AppVeyor, or using Test REST API, publish as Test Report

DupFinder

  • Errors will fail the Build
  • Report is surfaced as an artifact, regardless of build success/failure
  • XSL transform is performed on the report to make it human readable
  • When possible in AppVeyor, or using Test REST API, publish as Test Report

InspectCode

  • Errors will fail the Build
  • Report is surfaced as an artifact, regardless of build success/failure
  • XSL transform is performed on the report to make it human readable
  • When possible in AppVeyor, or using Test REST API, publish as Test Report

Metadata

Metadata

Assignees

Labels

ImprovementIssues that enhances existing functionality, or adds new features

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0