Skip to content

Update actions/checkout digest to b4ffde6 #841

Update actions/checkout digest to b4ffde6

Update actions/checkout digest to b4ffde6 #841

Triggered via push October 19, 2023 11:57
Status Success
Total duration 10m 34s
Artifacts 2

build.yml

on: push
Integration Tests Script Runner Windows (.NET Core tool)
4m 41s
Integration Tests Script Runner Windows (.NET Core tool)
Fit to window
Zoom out
Zoom in

Annotations

20 warnings
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/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/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)
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/PullRequestSystems/AzureDevOpsPullRequestSystem.cs#L162
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/PullRequestSystems/GitHubPullRequestSystem.cs#L8
Type 'GitHubPullRequestSystem' can be sealed because it has no subtypes in its containing assembly and is not externally visible (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1852)
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.
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1
Using directive should appear within a namespace declaration
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L2
Using directive should appear within a namespace declaration
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L3
Using directive should appear within a namespace declaration
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L4
Using directive should appear within a namespace declaration
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L5
Using directive should appear within a namespace declaration
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
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
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.
Integration Tests Script Runner Windows (.NET Core tool): tests/script-runner/src/ClassLibrary1/Class1.cs#L1
Using directive should appear within a namespace declaration

Artifacts

Produced during runtime
Name Size
Integration Tests Script Runner Windows (.NET Core tool) Expired
57.2 KB
NuGet Package Expired
101 KB