Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot list build defintions #198

Closed
2 of 7 tasks
colindembovsky opened this issue Sep 9, 2019 · 4 comments
Closed
2 of 7 tasks

Cannot list build defintions #198

colindembovsky opened this issue Sep 9, 2019 · 4 comments
Labels
bug when a bug has been identified or filed Investigating when an issue needs further investigation by a maintainer. Used only by maintainer.

Comments

@colindembovsky
Copy link

Steps to reproduce

Set-VSTeamAccount -Account devops-iaa-dryrun -PersonalAccessToken "mypat"
New-PSDrive -Name azdo -PSProvider SHiPS -Root 'VSTeam#VSTeamAccount'
cd azdo:
cd MyProject\Build Definitions
ls

Expected behavior

List of build definitions.

Actual behavior

ls : Item 'Build Definitions' may no longer exists. Details: The property 'name' cannot be found on this object.
Verify that the property exists..
At line:1 char:1
+ ls
+ ~~
    + CategoryInfo          : NotSpecified: (SHiPS:String) [Get-ChildItem], Exception
    + FullyQualifiedErrorId : PropertyNotFoundStrict,Get-VSTeamBuildDefinition,Microsoft.PowerShell.Commands.GetChildI
   temCommand

Environment data

OS

  • macOS
  • Windows
  • Linux

Server

  • TFS 2017
  • TFS 2018
  • Azure DevOps Server
  • Azure DevOps Service
> Get-VSTeamAPIVersion
Name                           Value
----                           -----
Release                        5.1-preview
Version                        VSTS
MemberEntitlementManagement    5.1-preview
DistributedTask                5.0-preview
Core                           5.0
Packaging                      5.1-preview
ServiceFabricEndpoint          5.0-preview
VariableGroups                 5.0-preview.1
Build                          5.0
Git                            5.1-preview
ExtensionsManagement           5.1-preview
Graph                          5.1-preview
Tfvc                           5.0
> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.18362.145
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.145
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
@DarqueWarrior DarqueWarrior added the Investigating when an issue needs further investigation by a maintainer. Used only by maintainer. label Nov 9, 2019
@richardgavel
Copy link

The mention of a YAML vs GUI on #216 had me research further and I did find it was choking only on GUI based pipelines. Ran the raw REST API and this is what I got, specifically around the embedded "queue" property:

GUI
"queue": { "_links": { "self": { "href": "https://dev.azure.com/xxx/_apis/build/Queues/26" } }, "id": 26, "url": "https://dev.azure.com/xxx/_apis/build/Queues/26", "pool": null },

YAML
"queue": { "_links": { "self": { "href": "https://dev.azure.com/xxx/_apis/build/Queues/235" } }, "id": 235, "name": "Self Hosted Docker (Windows 1903)", "url": "https://dev.azure.com/xxx/_apis/build/Queues/235", "pool": { "id": 26, "name": "Self Hosted Docker (Windows 1903)" } },

@SebastianSchuetze
Copy link
Collaborator

SebastianSchuetze commented Apr 25, 2020

@richardgavel could you help us in providing a solution for this? code snippets are enough. We can make the PR as well if it is not too much effort.

@SebastianSchuetze SebastianSchuetze added the bug when a bug has been identified or filed label Jul 4, 2020
@SebastianSchuetze
Copy link
Collaborator

@colindembovsky and @richardgavel do this problem still exist for you? I have tested it with both types of build definitions. But I don't have that problem.

Maybe it has been fixed because of another change in the API or with the code. But I cannot find for sure. It would help if you can try to reproduce it again.
Maybe it is a certain configuration that must exist on the build definitions to trigger that exception.

@DarqueWarrior
Copy link
Collaborator

I just tested today with both builds in the same project and it is working as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug when a bug has been identified or filed Investigating when an issue needs further investigation by a maintainer. Used only by maintainer.
Projects
None yet
Development

No branches or pull requests

4 participants