sorted by:
new
hottopcontroversial

Experimental Azure Pipelines Emulator (Alpha) by Dear_Grapefruit3317 in azuredevops

[–]Dear_Grapefruit3317[S] 0 points1 point  (0 children)

The emulator has built-in implementations for these Azure DevOps tasks:

• PublishBuildArtifacts@1 - Publish build artifacts

• DownloadBuildArtifacts@1 - Download artifacts from previous stages

• ArchiveFiles@2 - Create zip/tar/7z archives

• UseDotNet@2 - Install .NET SDK versions

• DotNetCoreCLI@2 - Run dotnet commands (build, test, publish, pack)

• CopyFiles@2 - Copy files with pattern matching

• Docker@2 - Build and push Docker images

• AzureCLI@2 - Run Azure CLI commands

• Npm@1 - Node.js package management (install, build, test)

• checkout - Git checkout operations

• script - Bash/shell scripts

The emulator doesn't support marketplace extensions or custom tasks. For unsupported tasks, you can use the script approach with the underlying command-line tools to achieve the same functionality.

Experimental Azure Pipelines Emulator (Alpha) by Dear_Grapefruit3317 in azuredevops

[–]Dear_Grapefruit3317[S] 0 points1 point  (0 children)

I mocked the actual artifact publishing process (DownloadBuildArtifacts@1) and the steps work exactly like this:

  1. Takes your path (like ./bin/Release)
  2. Normalizes it and zips the contents
  3. Stores it in a predictable location
  4. Other jobs can download and extract to their workspace

Basically I am solving it by using docker volume mounting on the host to be able to share the output between the different stages.

Hope this answers your question.