CODEWITHSUNDEEP
azureazure-devopsazure-pipelines
ashic
ashic

Reputation: 6495

Artifacts in Azure Devops Pipelines

I have an azure devops pipeline that publishes output like this:

steps:
- script: ./something.sh
  displayName: build
- publish: $(System.DefaultWorkingDirectory)/app/build
  artifact: MyPackage

This works, and publishes a build artefact, but it's not available in the Artifacts page of Azure devops, and the only way to get to it is through an http url. Is there some way to publish the artefact to the Artifacts page? In addition, the url to the artefact has the buildid in it. Is there a way I can specify semver version numbers?

Upvotes: 1

Views: 1356

Answers (1)

Krzysztof Madej
Krzysztof Madej

Reputation: 40849

If you want to have your package available in Azure Artifacts you should publish it to feed. Here you have an example with Universal Package.

Speaking about SemVer (from link above):

In Universal Packages, a particular package is identified by its name and version number. Currently, Universal Packages require Semantic Versioning. Semantic version numbers have three numeric components, Major.Minor.Patch. When you fix a bug, you increment the patch (1.0.0 to 1.0.1). When you release a new backward-compatible feature, you increment the minor version and reset the patch version to 0 (1.4.17 to 1.5.0). When you make a backward-incompatible change, you increment the major version and reset the minor and patch versions to 0 (2.6.5 to 3.0.0).

The Universal Packages task automatically selects the next major, minor, or patch version for you when you publish a new package. Just set the appropriate option.

And you build/pipeline artifact you will find here: enter image description here

Upvotes: 2

Related Questions