Skip to content

Getting Started

Russell Seymour edited this page Sep 14, 2017 · 3 revisions

Last updated: 14th September 2017

Please visit our blog post announcing the features of the extension:

ANNOUNCEMENT LINK

Prequisites

Habitat

You need to have an account set up with Habitat so that you have a an origin and public / private key. This will also require that you have a GitHub token so that Habitat packages can be uploaded to the Depot.

Build and Release phase tasks

Currently the tasks need to be run on your own private Linux agent. This is so that the extension is able to download Habitat and access sudo if and when it needs to.

To setup a private agent please refer to this Microsoft GitHub page.

When the agent is run it should be run under a normal user account that has the ability to use sudo without a password. For example if it was running under the account vsts then the following should be added to /etc/sudoers.d/vsts:

vsts ALL=(root) NOPASSWD:ALL

Each task has been labeled with the phase that is it designed for, but each task can be used in either phase.

Docker

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 VSTS tasks to upload it to the Docker Registry or a private one.

This is only required for the Tag an Image task.

The extension is still under active development and will move towards being able to use a Hosted agent and Windows agents.

Further Info

More information will appear on this Wiki as and when it is appropriate. In the meantime please visit our ANNOUNCEMENT LINK page.