CODEWITHSUNDEEP
githubazure-devopsazure-pipelines
ekolis
ekolis

Reputation: 6806

How do I make a release pipeline in Azure DevOps that creates a GitHub release every time?

I get this warning when the pipeline runs:

Release will not be created as the tags for the target commit do not match with the given tag pattern.

Thing is, the Tag Pattern property of the GitHub release is blank; I'm not setting any particular tag pattern. How do I skip this warning so the release can be created every time the pipeline runs?

Upvotes: 6

Views: 2477

Answers (1)

Leo Liu
Leo Liu

Reputation: 76928

How do I make a release pipeline in Azure DevOps that creates a GitHub release every time?

I could reproduce this issue on my side, if I leave the Tag Pattern property of the GitHub release is blank.

That because this property is Required. Check the GitHub Release task:

Tag source (Required) Configure the tag to be used for release creation. The 'Git tag' option automatically takes the tag which is associated with this commit. Use the 'User specified tag' option in case you want to manually provide a tag.

As the description above, the 'Git tag' option automatically takes the tag which is

associated with this commit.

So, if we leave that property Tag Pattern is blank, the value is null, but the commit id is not null, then you will get this error. Check my detailed build log:

enter image description here

To resolve this issue, we could give the Tag Pattern with the commit ID. Or you could use the another option User specified tag, then you can manually provide a tag, like release-v1.0.

As test, it works fine on my side.

Update:

but I want the pipeline to run every time someone pushes or merges code into the master branch; I don't want to have to specify a tag for each commit

If you do not want to have to specify a tag for each commit, you can use counter expressions in Variables, like:

variables:
  MajorVersion: 1
  MinorVersion: 0
  InitialReleaseTagNumber: 1
  IncrementReleaseTagNumber: $[counter(variables['InitialReleaseTagNumber'], 0)]

Then we set v$(MajorVersion).$(MinorVersion).$(IncrementReleaseTagNumber) following in the tag option:

enter image description here

So, the value of the tag will increase by 1 once the build runs.

Hope this helps.

Upvotes: 6

Related Questions