This repository contains source code, documentation and scripts required to build and publish the Apwide Golive for Jira Azure DevOps extension: https://marketplace.visualstudio.com/items?itemName=Apwide.ApwideGoliveForJiraDev
-
Create a personal access token for the Azure Devops account where you would test run your task. Refer this to learn how to create a personal access token.
-
Request to have permission on different Apwide project/organization (to upload task and so on such as Apwide Organization, its projects, being member of "Project Collection Administrators" organization group, having permission to access Apwide publisher)
-
Set following environment variables to enable inner loop commands-
BUILD_ENV= developmentADO_PAT- Your personal access tokenADO_ACCOUNT_URI- The default collection URI for your account (eg. https://dev.azure.com/{{name}})DEV_PUBLISHER- Id of your publisher account
-
Run following commands to verify setup-
npm install(Installs npm dependencies)npm run dev(Builds, packages and publishes the extension)
-
Refer to package.json to see the list of all commands.
| What changed? | Which NPM command to run? | What it does? |
|---|---|---|
| Task implementation | npm run dev:{task-name} |
Build, package and update custom task without updating extension (Faster) |
| Anything else | npm run dev |
Build, package and publish full extension (Slower) |
- you will not be able to publish the extension to the marketplace between 00:00 and 01:00 (AM)
- do not forget to set the environment variables correctly
- updates of some common resources may conflict when both "DEV" and "PROD" versions of the extension are installed to the same Azure DevOps organization
- multiple versions of same task: https://stackoverflow.com/questions/43789135/tfs-custom-build-tasks-multiple-versions
Test tf CLI on linux (https://github.com/microsoft/team-explorer-everywhere)