Build and tests

Update Cake.Issues.MsBuild to 4.0.0-beta0001 #531

Sign in to view logs

Triggered via push December 9, 2023 23:11

feature/gh-390

Status Success

Total duration 7m 38s

Artifacts 2

build.yml

on: push

Integration Tests Script Runner Windows (.NET Core tool)

Annotations

20 warnings

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/RepositoryInfo/CliRepositoryInfoProvider.cs#L54

Prefer comparing 'Length' to 0 rather than using 'Any()', both for clarity and for performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1860)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/RepositoryInfo/CliRepositoryInfoProvider.cs#L76

Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/BuildServers/AzureDevOpsBuildServer.cs#L55

Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/BuildServers/AzureDevOpsBuildServer.cs#L101

Exception type System.ApplicationException is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/BuildServers/AzureDevOpsBuildServer.cs#L55

Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/RepositoryInfo/CliRepositoryInfoProvider.cs#L76

Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/BuildServers/AzureDevOpsBuildServer.cs#L101

Exception type System.ApplicationException is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/PullRequestSystems/AzureDevOpsPullRequestSystem.cs#L133

Possible multiple enumerations of 'IEnumerable' collection. Consider using an implementation that avoids multiple enumerations. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1851)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/RepositoryInfo/CliRepositoryInfoProvider.cs#L76

Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)

Build: Cake.Frosting.Issues.Recipe/Cake.Frosting.Issues.Recipe/PullRequestSystems/AzureDevOpsPullRequestSystem.cs#L151

Possible multiple enumerations of 'IEnumerable' collection. Consider using an implementation that avoids multiple enumerations. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1851)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1

The file header is missing or not located at the top of the file. (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1633.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L2

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L3

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L4

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L5

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L21

Member 'Bar' does not access instance data and can be marked as static (https://docs.microsoft.com/visualstudio/code-quality/ca1822)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L11

Member 'Foo' does not access instance data and can be marked as static (https://docs.microsoft.com/visualstudio/code-quality/ca1822)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1

The file header is missing or not located at the top of the file. (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1633.md)

Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1

Using directive should appear within a namespace declaration (https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA1200.md)

Artifacts

Produced during runtime

Name	Size
Integration Tests Script Runner Windows (.NET Core tool) Expired	59.4 KB
NuGet Package Expired	124 KB