Please visit our blog post announcing the features of the extension:
You need to have an account set up with Habitat so that you have a an origin and public / private key.
You will also need to create a Personal Access Token (PAT) on your Habitat Builder Profile page. This information is required to upload built packages to the Habitat depot.
From Habitat version 0.81 onwards a license must be accepted before the software can be used. To do this add a variable to the pipeline:
This can be done in the Azure DevOps UI or within a pipeline file.
variables: - name: HAB_LICENSE value: accept-no-persist
Build and Release phase tasks
Each task has been labeled with the phase that is it designed for, but each task can be used in either phase.
If you want to be able to export a Habitat package as a Docker image then you will need to ensure that Docker is installed in your agent. The resulting image can then be used with other Azure DevOps tasks to upload it to the Docker Registry or a private one.
This is only required for the [[Tag an Image]] task.
More information will appear on this site as and when it is appropriate. In the meantime please visit our Habitat Integration for Azure DevOps in the Visual Studio Marketplace page.Azure DevOps