Skip to content
This repository has been archived by the owner on Jan 25, 2022. It is now read-only.

[WIP] AzureDevops rebranding changes #13

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

norschel
Copy link

Due to the rebranding of TFS/VSTS to Azure DevOps, some adjustments to libraries and categories in the Extension Manifest are necessary.
As part of the PR, the hardcoded category was replaced by a token, so that build processes can create two variants for old and new versions of the TFS/VSTS/Azure DevOps platform from a single code base.

Nico Orschel added 6 commits December 22, 2018 20:25
…ebranding TFS/VSTS to Azure DevOps, replaced extension category with placeholder so that we can produce two versions of the extensions using a build process and token replacement
@matthid matthid self-requested a review February 12, 2019 19:32
@@ -1,4 +1,12 @@
# How to build
Notice:
To build locally you have to change the attribute Categories in the file vss-extension.json.
If you want a local deployment of the extension for TFS 2018 and older, replace the value __ExtensionCategory___ with "Build and release".
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that mean "Build and release" no longer works at all, did they break this?
If this still works I'd suggest to keep that. If this indeed doesn't work anymore I feel like it is easier to just replace it with "Azure Pipelines" in vss-extension and add a patch-file/sed-command or a second vssextension.json file.
This way I can clone and build and don't need to edit files ;)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants