azp: Running more than one VSBuild task in a single job fails

[fmemb]

First want to say, that you've created a really awesome tool.
I'm sure it could help us a lot in our daily work.

Unfortunately I can't get it to run my azure pipeline file.

I have a pipeline with several VSBuild build tasks run sequentially in a single job.
This seems to cause issues.

The runner stops processing all following job steps after second VSBuild build task completes.
The job reports success although all other job steps were skipped.
In the output there is no error reported.

I tested with .NET Framework VS projects (csproj).

I've put together a small azure pipeline file to reproduce the issue:

trigger: none

stages:
- stage: build
  jobs:
  - job:
    steps:
    - task: VSBuild@1
      inputs:
        solution: 'ClassLibrary1\ClassLibrary1.csproj'
        vsVersion: '17.0'
        configuration: 'Release'
        logProjectEvents: true
        createLogFile: true
        logFileVerbosity: 'detailed'
        msbuildArgs: '/p:TargetFrameworkVersion=v4.8.1'
    - task: VSBuild@1
      inputs:
        solution: 'ClassLibrary2\ClassLibrary2.csproj'
        vsVersion: '17.0'
        configuration: 'Release'
        logProjectEvents: true
        createLogFile: true
        logFileVerbosity: 'detailed'
        msbuildArgs: '/p:TargetFrameworkVersion=v4.8.1'
    - task: CmdLine@2
      inputs:
        script: |
          echo "Never reaches this task"
    - task: VSBuild@1
      inputs:
        solution: 'ConsoleApp1\ConsoleApp1.csproj'
        vsVersion: '17.0'
        configuration: 'Release'
        logProjectEvents: true
        createLogFile: true
        logFileVerbosity: 'detailed'
        msbuildArgs: '/p:TargetFrameworkVersion=v4.8.1'

Running this pipeline will stop after the second task.
Task 3 and 4 are not executed:

| Build succeeded.
| 0 Warning(s)
| 0 Error(s)
|
| Time Elapsed 00:00:00.41
| ##[section]Finishing: Build solution ClassLibrary2\ClassLibrary2.csproj
[azure-pipelines2.yml / build / Job] Job Completed with Status: Succeeded
[azure-pipelines2.yml] Workflow 1 Completed with Status: Succeeded
Where do you want to store your generated Workflow Artifacts? ( Leave empty to discard them ):
All Workflows finished successfully
Stopped Runner
Stopped Server

[ChristopherHX]

Thank you for your bug report.

I can reproduce this defect on windows using release 3.12.1, seems to be a regression of my 3.12 release.

Release 3.11 shows symptoms of http 500 errors as well in _diag logs of the agent, but no missing logs.

This problem seems to be fixed by #481, preventing the failure to update the timeline of the job.

I plan to do the next release 3.13 in a few days including this fix.

You can try an artifact of the current main branch as well: https://github.com/ChristopherHX/runner.server/actions/runs/13018156100 while I prepare the next release

used this sightly modified repository for validation: https://github.com/ChristopherHX/azure-pipelines-dotnet-4.7-sample

[fmemb]

Thank you for the quick resolution!
Amazing support!

I've tested with the version you provided and it works fine now.
All tasks are executed now.

[ChristopherHX]

Done released in https://github.com/ChristopherHX/runner.server/releases/tag/v3.13.1 (version v3.13.0 has been taken by a gh cli extension prerelease)

Please let me know if you find something else misbehaving to make this an even better tool.