Skip to content
Build and tests

Use Node 20 in integration tests #551

Sign in to view logs

Use Node 20 in integration tests

Use Node 20 in integration tests #551

Triggered via push March 8, 2024 14:30
@pascalbergerpascalberger
pushed 4ed169b
feature/fix-build
Status Success
Total duration 7m 43s
Artifacts 2

build.yml

on: push
Build
4m 10s
Build
Integration Tests Script Runner Windows (.NET Core tool)
3m 11s
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/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/BuildServers/AzureDevOpsBuildServer.cs#L55
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#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#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#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.05 KB
NuGet Package Expired
109 KB