Signtool telemetry fails for Linux files in release pipeline
See original GitHub issue- This issue is blocking
- This issue is causing unreasonable pain
Signtool telemetry errors after signing linux files in release pipeline.
This is the error
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: The "Microsoft.DotNet.SignTool.SignToolTask" task failed unexpectedly.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: System.TypeInitializationException: The type initializer for 'Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource' threw an exception.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: ---> System.NullReferenceException: Object reference not set to an instance of an object.
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.CounterGroup.OnEventSourceCommand(Object sender, EventCommandEventArgs e)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.EventSource.add_EventCommandExecuted(EventHandler`1 value)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.CounterGroup.RegisterCommandCallback()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.CounterGroup..ctor(EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.CounterGroup.GetCounterGroup(EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.DiagnosticCounter.Publish()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at System.Diagnostics.Tracing.EventCounter..ctor(String name, EventSource eventSource)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource..ctor()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource..cctor()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: --- End of inner exception stack trace ---
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.Tracing.CoreEventSource.get_IsVerboseEnabled()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Channel.InMemoryChannel.Send(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.TransmissionProcessor.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChain.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.TelemetrySink.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Shared.Extensibility.Implementation.PassThroughProcessor.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.Extensibility.Implementation.TelemetryProcessorChain.Process(ITelemetry item)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.TelemetryClient.Track(ITelemetry telemetry)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.TelemetryClient.TrackEvent(EventTelemetry telemetry)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.ApplicationInsights.TelemetryClient.TrackEvent(String eventName, IDictionary`2 properties, IDictionary`2 metrics)
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.DotNet.SignTool.Telemetry.SendEvents() in /_/src/Microsoft.DotNet.SignTool/src/Telemetry.cs:line 40
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.DotNet.SignTool.SignToolTask.ExecuteImpl() in /_/src/Microsoft.DotNet.SignTool/src/SignToolTask.cs:line 266
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.DotNet.SignTool.SignToolTask.Execute() in /_/src/Microsoft.DotNet.SignTool/src/SignToolTask.cs:line 154
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
D:\workspace\_work\1\s\src\Microsoft.DotNet.Release\Microsoft.DotNet.Signing.Extensions\SignLinuxPackages.proj(37,9): error MSB4018: --- End of stack trace from previous location ---
this is sample build -> https://dev.azure.com/dnceng/internal/_build/results?buildId=1227813&view=logs&j=d7f318d2-3658-5f56-29df-16b211ec56a6&t=7851342b-b7f6-561e-0dbe-e63708dfa83e
Versions :
SignToolVersion : 6.0.0-beta.21357.3 FeedsTaskVersion : 6.0.0-beta.21357.3
Issue Analytics
- State:
- Created 2 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
System.TypeInitializationException: The type initializer for ' ...
Introducing linux signing in Release pipeline, previously we used a separate pipeline to sign linux files-> https://dnceng.visualstudio.com/internal/_build?
Read more >Getting a "No certificates were found" error in an Azure ...
I'm working on migrating a TFS build/release to Azure DevOps Services (ADS) for a WPF app. The build works fine, but I'm having...
Read more >Explude Pipeline / Release from failed/not completed ...
Often you have to try things 5 or 6 times and when it fails it sends out a notification via mail to everyone...
Read more >Build pipeline CI trigger not firing - Developer Community
We have a YAML pipeline set to trigger on pushes to certain branches ... trigger: branches: include: - develop - release - master...
Read more >UWP app signing fails since vmImage-2022
When building an app on devops pipeline using this (part of the yaml) we recently are getting errors - task: VSBuild@1 inputs: platform: ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes I followed up and created an issue in application insights -https://github.com/microsoft/ApplicationInsights-dotnet/issues/2323 no response yet.
Agreed. I mentioned that in previous discussions, and also that it’s unclear when / if it will be fixed. The quirk being that the appinsights issue is specifically related to core, but sign tool runs on framework. Here was my comment around that…
I mention that if only to say that the important thing is the last thing I wrote. We should make sure we’re communicating with the app insights team about this and at least relaying our scenario (framework). It would be disappointing if they decided to finally fix this but only for core and we remain broken even longer than necessary. They might also say “no, that’s something else”. Which is a fine response.