Nuke and Azure Devops Microsoft Hosted Agent

[epsmae]

I am trying to get nuke running on azure devops with a microsoft hostet agent.
The agents can switch between the jobs, this result in the error that the restore may is executed on a different agent than the compile and therefore the packages are missing.

May I missed something? I use these atributes:

[CheckBuildProjectConfigurations]
[ShutdownDotNetAfterServerBuild]
InvokedTargets = new[] { nameof(Clean), nameof(Restore), nameof(Compile), nameof(Test), nameof(Pack) })]
class Build : NukeBuild
...

Which generates the following pipline.yaml

stages:
  - stage: windows_latest
    displayName: 'windows-latest'
    dependsOn: [  ]
    pool:
      vmImage: 'windows-latest'
    jobs:
      - job: Clean
        displayName: 'Clean'
        dependsOn: [  ]
        steps:
          - task: CmdLine@2
            inputs:
              script: './build.cmd Clean --skip'
      - job: Restore
        displayName: 'Restore'
        dependsOn: [ Clean ]
        steps:
          - task: CmdLine@2
            inputs:
              script: './build.cmd Restore --skip'
      - job: Compile
        displayName: 'Compile'
        dependsOn: [ Restore ]
        steps:
          - task: CmdLine@2
            inputs:
              script: './build.cmd Compile --skip'
      - job: Test
        displayName: 'Test'
        dependsOn: [ Compile ]
        steps:
          - task: CmdLine@2
            inputs:
              script: './build.cmd Test --skip'
      - job: Pack
        displayName: 'Pack'
        dependsOn: [ Test ]
        steps:
          - task: CmdLine@2
            inputs:
              script: './build.cmd Pack --skip'

[epsmae]

In the meantime I found out that I can set the no entry attribute like in the sample:
[AzurePipelines( suffix: null, AzurePipelinesImage.UbuntuLatest, AzurePipelinesImage.WindowsLatest, AzurePipelinesImage.MacOsLatest, InvokedTargets = new[] { nameof(Test), nameof(Pack) }, NonEntryTargets = new[] { nameof(Restore), nameof(DownloadFonts), nameof(InstallFonts), nameof(ReleaseImage) }, ExcludedTargets = new[] { nameof(Clean), nameof(Coverage), nameof(SignPackages) })]

However I would like to have them in one stage as jobs. As multiple stages increase the build time a lot.

[arialdomartini]

I'm experiencing the same. Did you manage to find out how to deal with this problem?
If there are no workarounds, Unfortunately this is for us a show stopper.

Edit: we are thinking of writing the YML manually, and completely get rid of the automated generation performed by the AzurePipelines attribute.

[epsmae]

@arialdomartini I did not further investigate as we finally use Bitbucket.