Skip to content
Build and tests

Fix issues with different provider on issue than on provider #646

Sign in to view logs

Fix issues with different provider on issue than on provider

Fix issues with different provider on issue than on provider #646

Triggered via push July 18, 2024 18:08
@pascalbergerpascalberger
pushed 8d175cb
feature/gh-474
Status Success
Total duration 10m 43s
Artifacts 2

build.yml

on: push
Build
7m 7s
Build
Integration Tests Script Runner Windows (.NET Core tool)
3m 13s
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/RepositoryInfo/CliRepositoryInfoProvider.cs#L72
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#L50
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#L96
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#L50
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#L72
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#L72
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#L96
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#L50
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#L96
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#L72
Exception type System.Exception is not sufficiently specific (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2201)
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
5.08 KB
NuGet Package Expired
119 KB