search

geeklearningio / gl-vsts-tasks-yarn

Yarn Package Manager Visual Studio Team Services Build and Release Management extensions
MIT License
52 stars 18 forks source link

Latest release (2.7.1001) broken custom registries #58

Closed Lrimas closed 5 years ago

Lrimas commented 5 years ago

Before opening an issue please read this.

Are you reporting a bug or a feature request ?

Bug

Description

The most recent release (2.7.1001) appears to have broken the custom registries. We are getting an error on all of our builds that use the yarn task: capture

This is a custom repository in Azure Devops (VSTS). When I click on the dropdown box there are 'no results found'

The functionality was working before the update and I can confirm that tasks that use NuGet are still working. In other words, I do not believe that the issue is with our repository.

Expected behavior

The yarn task should allow you to select an Azure Devops repository

Reproduction

  1. Insert yarn task in Azure Devops Builds
  2. Select "Use packages from this VSTS/TFS registry"
  3. Dropdown box does not supply list of VSTS registries.
MANDATORY FOR BUGS: Insert debug trace

In order to allow us to quickly reproduce you issue please include a link to a reproduction repository

System information

VSTS or TFS:

Agent:

OS:

Yarn version: *Yarn version**

Node version: *Node version**

berickson1 commented 5 years ago

+1, came here to file the same thing. Seeing this on (Version 2.7.999) as well

sandorfr commented 5 years ago

Hi @berickson1 and @Lrimas,

Sorry about that. I reproduced it and I just pushed an update which solves the problem.

Let me know how it goes for you.

Lrimas commented 5 years ago

@sandorfr - I can confirm that this is now fixed. Thank you very much!

sandorfr commented 5 years ago

Thanks for the update.

berickson1 commented 5 years ago

Likewise, seems to be working again. Thanks @sandorfr