Menu
I develop an Azure DevOps extension. Now I want to automate the publishing process. Here the journey begins ... Following the theory here the reality looks different to me.
For me every trial of publish via command line ends in
tfx extension publish --auth-type pat -t
7dblablablablablablablablazq --share-with examplecompany0123
TFS Cross Platform Command Line Interface v0.6.3
Copyright Microsoft Corporation
Checking if this extension is already published
It isn't, create a new extension.
error: Received response 401 (Not Authorized). Check that your personal
access token is correct and hasn't expired.
My first guess on that error message 401 was that I probably have a wrong PAT. A look in my PAT management showed me that everything seems good.
So, now I am confronted like a cow at a five-barred gate. I just don't get the root of the failure. Anyone here who already has left this noob beginner problems behind and reached the next level and can help me?
244
Publish your extensionFrom the management portal, select your publisher from the drop-down menu at the top of the page. Select New extension > Azure DevOps. Drag and drop your file or select it to find your VSIX file, which you created in the previous packaging step, and then choose Upload.
Approve an extension requestGo to your Azure DevOps project, https://dev.azure.com/{organization}/{project} . Select the shopping bag icon, and then Manage extensions. Review and approve your requested extensions. After you approve extension requests, the extensions are automatically installed.
From your Azure DevOps Server home page ( https://{server}:8080/tfs/ ), go to the project collection where you want to install the extension. Open the extensions menu and choose Browse Marketplace. Find and select the extension that you want to install. Select the extension, and then Install.
Ensure your PAT have Account: 'All accessible organizations'.
168
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
