CODEWITHSUNDEEP
azure-devops
Scott Ocamb
Scott Ocamb

Reputation: 25

Unique Need - Perform Team Services releases using artifacts created in an external build

I have a unique need where I need to perform releases from Team Services using a Release Pipeline and artifacts that have been created in a previous external build. I have the artifacts that were created, dacpacs and websites ect.

I would like to deploy these items using the features in release Pipelines but artifact sources only come from a build or some other version control.

My approach (hack) was to use a build to copy the external files and publish them into the artifact container for the build. I could then use the release pipelines to do my releases. But .. Build copy tasks only seem to work with paths into a repo.

My fall back will be to use the release pipeline and powershell to do the releases with these externally created artifacts. I would sure like to avoid this since there is nice capability in the release pipeline tasks.

This is a compliance requirement my firm has which results in the rather crazy post.

Any help would really be appreciated.

Upvotes: 0

Views: 142

Answers (1)

Marina Liu
Marina Liu

Reputation: 38096

You can use Copy Files task and Publish Build Artifacts task for your build definition.

Copy Files task

  • Source Folder: you can specify the folder which has your external build artifacts. Such as C:\project\a.

  • Contents: you can use wildcards to specify which files to copy. Such as **\*.dll, this will copy all *.dll files in C:\project\a and it’s subfilder.

  • Target Folder: where you want to copy these files. Usually it’s $(build.artifactstagingdirectory).

Publish Build Artifacts task

  • Path to Publish: set as the same with Target folder in Copy files task. Such as $(build.artifactstagingdirectory).

Note: Copy files task will find the source folder in the machine where the private agent is located.

Upvotes: 0

Related Questions