Error: The process dotnet.exe failed with exit code 1

[verback2308]

Description

Copied from Azure Pipelines Tasks

All our pipelines started crashing with an error on dotnet publish since last Saturday (September 14):

There are no details in the logs except that the command returned error 1:

Version of the last successful pipeline the same as other - 2.245.1

Old pipelines for previous branches were checked - they also started crashing with an error, however - code is the same:

Diff between latest successful (left) and current (right) build:

Temporarily switched to a self-hosted agent, everything works there.
Solution compiles on a dev machine (osx, win) with a success.

upd1: just found a workaround - added step with SDK installation:

- task: UseDotNet@2 
displayName: 'Install .NET Core SDK' 
inputs: version: 7.x 
performMultiLevelLookup: true 
includePreviewVersions: true # Required for preview versions

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 12
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• Windows Server 2019
• Windows Server 2022

Image version and build link

Image: windows-2022
Version: 20240912.1.0
Included Software: https://github.com/actions/runner-images/blob/win22/20240912.1/images/windows/Windows2022-Readme.md
Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240912.1

Is it regression?

Expected behavior

Build should finish with a success

Actual behavior

The process dotnet.exe failed with exit code 1

Repro steps

pool:
  vmImage: 'windows-latest'

variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages
  pvs-solution: 'PVS/PVS.sln'
  client: 'PVS.Clients.WebClient.Core'

steps:

  - task: NuGetToolInstaller@1
    displayName: 'Install NuGet'

  - task: Cache@2
    displayName: 'NuGet Cache'
    inputs:
      key: 'nuget | "$(Agent.OS)" | **/packages.lock.json,!**/bin/**,!**/obj/**'
      restoreKeys: |
        nuget | "$(Agent.OS)"
        nuget
      path: '$(NUGET_PACKAGES)'
      cacheHitVar: 'CACHE_RESTORED'

  - task: NuGetCommand@2
    displayName: 'Restore NuGet packages for PVS'
    condition: ne(variables.CACHE_RESTORED, true)
    inputs:
      command: 'restore'
      restoreSolution: '$(pvs-solution)'
      feedsToUse: 'config'
      nugetConfigPath: 'PVS/NuGet.Config'

  - task: DotNetCoreCLI@2
    displayName: 'Publish $(Client)'
    inputs:
      command: 'publish'
      publishWebProjects: false
      projects: 'PVS/$(Client)/$(Client).csproj'
      arguments: '-c Release --no-self-contained -f net7.0 /p:ExcludeApp_Data=False -o "$(Build.BinariesDirectory)/$(Client)"'
      zipAfterPublish: false
      modifyOutputPath: false

[SotnikovMaksym]

Description

Copied from Azure Pipelines Tasks

All our pipelines started crashing with an error on dotnet publish since last Saturday (September 14):

There are no details in the logs except that the command returned error 1:

Version of the last successful pipeline the same as other - 2.245.1

Old pipelines for previous branches were checked - they also started crashing with an error, however - code is the same:

Diff between latest successful (left) and current (right) build:

Temporarily switched to a self-hosted agent, everything works there. Solution compiles on a dev machine (osx, win) with a success.

upd1: just found a workaround - added step with SDK installation: - task: UseDotNet@2 displayName: 'Install .NET Core SDK' inputs: version: 7.x performMultiLevelLookup: true includePreviewVersions: true # Required for preview versions

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• Ubuntu 24.04
• macOS 12
• macOS 13
• macOS 13 Arm64
• macOS 14
• macOS 14 Arm64
• Windows Server 2019
• Windows Server 2022

Image version and build link

Image: windows-2022 Version: 20240912.1.0 Included Software: https://github.com/actions/runner-images/blob/win22/20240912.1/images/windows/Windows2022-Readme.md Image Release: https://github.com/actions/runner-images/releases/tag/win22%2F20240912.1

Is it regression?

Expected behavior

Build should finish with a success

Actual behavior

The process dotnet.exe failed with exit code 1

Repro steps

pool:
  vmImage: 'windows-latest'

variables:
  NUGET_PACKAGES: $(Pipeline.Workspace)/.nuget/packages
  pvs-solution: 'PVS/PVS.sln'
  client: 'PVS.Clients.WebClient.Core'

steps:

  - task: NuGetToolInstaller@1
    displayName: 'Install NuGet'

  - task: Cache@2
    displayName: 'NuGet Cache'
    inputs:
      key: 'nuget | "$(Agent.OS)" | **/packages.lock.json,!**/bin/**,!**/obj/**'
      restoreKeys: |
        nuget | "$(Agent.OS)"
        nuget
      path: '$(NUGET_PACKAGES)'
      cacheHitVar: 'CACHE_RESTORED'

  - task: NuGetCommand@2
    displayName: 'Restore NuGet packages for PVS'
    condition: ne(variables.CACHE_RESTORED, true)
    inputs:
      command: 'restore'
      restoreSolution: '$(pvs-solution)'
      feedsToUse: 'config'
      nugetConfigPath: 'PVS/NuGet.Config'

  - task: DotNetCoreCLI@2
    displayName: 'Publish $(Client)'
    inputs:
      command: 'publish'
      publishWebProjects: false
      projects: 'PVS/$(Client)/$(Client).csproj'
      arguments: '-c Release --no-self-contained -f net7.0 /p:ExcludeApp_Data=False -o "$(Build.BinariesDirectory)/$(Client)"'
      zipAfterPublish: false
      modifyOutputPath: false

Have the same problem since Friday the 13th of September!

[kishorekumar-anchala]

Hi @verback2308 ,

Thank you for bringing this issue to us. We are looking into this issue and will update you on this issue after investigating.

[kishorekumar-anchala]

Hi @verback2308 ,

Could you please try to build with latest version 20240915.1 . thank you !

[kishorekumar-anchala]

HI @verback2308 ,

  Could you please share your update on this issue ?

[kishorekumar-anchala]

HI @verback2308 ,

We’ve tried reaching out to you regarding this issue, but since we haven’t received a response, we will be closing it. We hope the recent rollout has resolved your concerns. Thank you!

[verback2308]

Hi, @kishorekumar-anchala
Sorry for a delayed response, was on vacation.
Seem now everything good. Thank you.