GoReleaser: Azure DevOps Extension

Overview

This task allows you to easily run GoReleaser within your Azure Pipeline jobs.

Howto

See the blog article Use GoReleaser With Azure DevOps for a detailed explanation of how to use this extension in your Azure Pipeline jobs.

QuickStart

Customizing

Add the plugin via Azure Pipeline Editor

or directly into your azure-pipeline.yaml

- task: goreleaser@0
  inputs:
    version: 'latest'
    distribution: 'goreleaser'
    args: ''
    workdir: '$(Build.SourcesDirectory)'

Inputs

Following inputs can be used

Name	Type	Default	Description
distribution	String	goreleaser	GoReleaser distribution, either goreleaser or goreleaser-pro
version¹	String	latest	GoReleaser version
args	String		Arguments to pass to GoReleaser
workdir	String	$(Build.SourcesDirectory)	Working directory (below repository root)
installOnly	Bool	false	Just install GoReleaser

¹ Can be a fixed version like v0.132.0 or a max satisfying semver one like ~> 0.132. In this case this will return v0.132.1. For the pro version, add -pro to the string

Environment variables

Following environment variables can be used, as environment variable.

Name	Description
GITHUB_TOKEN	GITHUB_TOKEN for e.g. brew or gofish
GORELEASER_KEY	Your GoReleaser Pro License Key, in case you are using the goreleaser-pro distribution

Limitation

I think, you should either disable the release step. Or create a " dummy" repo in GitHub, so you can still use your own homebrew tap or gofish repo.

GoReleaser is not supporting Azure Artifacts currently.

You need to use Publish Pipeline Artifacts to publish the artifact inside Azure DevOps.

Tutorials

• Use GoReleaser With Azure DevOps
• Releasing multi-platform container images with GoReleaser in Azure DevOps

Documentation

Please refer to https://goreleaser.com/intro/ for more documentation on using GoReleaser.

Links

• Follow the progress on the GitHub repository
• Follow @goreleaser on Twitter for updates
• Join our Discord server
• Ask questions on StackOverflow
• For questions, support and general discussion, please use GitHub Discussions;
• Contributing Guidelines

License

MIT

see LICENSE for details.