darquewarrior / generator-team Goto Github PK

This will allow users to add additional apps to the same team project.

This will be added once it is supported on VSTS hosted build agents.

This is my first attempt so it might be me.

NPM Version 4.1.2
yo Version 1.8.5
generator-team Version 0.1.3

When running yo team from a PowerShell window I get the following error message:

~\Source\Repos> yo team
C:\Users\Dave\AppData\Roaming\npm\node_modules\generator-team\generators\app\index.js:48
   let cmdLnInput = this;
   ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.defineProperty.get [as team:app] (C:\Users\Dave\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\lib\store.js:40:23)
    at Store.get (C:\Users\Dave\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\lib\store.js:64:35)
    at Environment.get (C:\Users\Dave\AppData\Roaming\npm\node_modules\yo\node_modules\yeoman-environment\lib\environment.js:262:16)

I can't connect to Azure App Service in Azure China Cloud, whether yoteam enable to connect Azure China Cloud(Azure Mooncake)?

Can you please add deployment options to Kubernetes clusters like private and/or AKS?

The current generator for ASP.NET Core projects is still pointing to 1.1 which was admittedly the latest RTM till about 3 weeks ago. The latest release of .NET 2.0 means that the build template needs to use the latest released one on VSTS (including the custom download of the latest version of NuGet.exe)

If you point me to the right direction, I'll be happy to take a stub at it and raise a PR for you

Hi Donovan,

Running the yo team generator, I get as far as creating the CI Build and it errors on me:

Any ideas what went wrong with the generator?

Thanks in advance,
Mark

? Enter Team Services account name
({account}.visualstudio.com)
Or full TFS URL including collection
(http://tfs:8080/tfs/DefaultCollection)? https://markarrowsmith.visualstudio.com
? What is your TFS Personal Access Token? ****************************************************
Getting Agent Queues...
? What agent queue would you like to use? Default
? What type of application do you want to create? .NET Core
? What is the name of your application? yo-vsts-demo
? Where would you like to deploy? Azure App Service
? What is your Azure subscription name? Visual Studio Ultimate with MSDN
? What is your Azure subscription ID? *******************************************
? What is your Azure Tenant ID? *******************************************
? What is your Service Principal ID? *******************************************
? What is your Service Principal Key? ********************************************
? Install dependencies? Yes

• Creating yo-vsts-demo Team Project
• Cloning repository https://markarrowsmith.visualstudio.com/_git/yo-vsts-demo
  warning: invalid credential line: [0x7FFECFFB70E3] ANOMALY: use of REX.w is meaningless (default operand size is 64)
  warning: You appear to have cloned an empty repository.
• Creating Visual Studio Ultimate with MSDN Azure Service Endpoint
• Creating CI build definition
  undefined:3

^

SyntaxError: Unexpected token < in JSON at position 4
at Object.parse (native)
at Request._callback (C:\Users\marro\AppData\Roaming\npm\node_modules\generator-team\generators\app\utility.js:615:22)
at Request.self.callback (C:\Users\marro\AppData\Roaming\npm\node_modules\generator-team\node_modules\request\request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (C:\Users\marro\AppData\Roaming\npm\node_modules\generator-team\node_modules\request\request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage. (C:\Users\marro\AppData\Roaming\npm\node_modules\generator-team\node_modules\request\request.js:1091:12)
at IncomingMessage.g (events.js:286:16)

c:\Dev\yo-team-demo>

while using yo team to build a demo project.

C:\Users\tfsadmin>yo team

 _-----_     ╭──────────────────────────╮
|       |    │     Welcome to DevOps    │
|--(o)--|    │   powered by Microsoft   │

---------´ │ version 0.4.5 │ ( _´U_ ) ╰──────────────────────────╯
/A\ /
| ~ |
'..'_
´ |° ´ Y

? Enter VSTS account name
({account}.visualstudio.com)
Or full TFS URL including collection
(http://tfs:8080/tfs/DefaultCollection)
Or name of a stored Profile? http://:@139.217../DefaultCollection
? What is your TFS Personal Access Token? [hidden]
Getting Agent Queues...
? What agent queue would you like to use? Default
? What type of application do you want to create? .NET Core
? What is the name of your application? YoTeamDemoApp
? Where would you like to deploy? Azure App Service
? What is your Azure subscription name? Visual Studio Enterprise - MPN
? What is your Azure subscription ID? 1dc8df9f-9d86-4633-8cfe-****
? What is your Azure Tenant ID? 314999a7-b7c5-4b6a-96ea-********
? What is your Service Principal ID? 988086db-5b0e-42b7-b635-********
? What is your Service Principal Key? [hidden]
? Install dependencies? No

• Found Team project
• Cloning repository http://:@139.217..***/DefaultCollection/_git/YoTeamDemoApp
  warning: You appear to have cloned an empty repository.
• Found Azure Service Endpoint 'Visual Studio Enterprise - MPN'

�[?25hC:\Program Files\nodejs\node_global\node_modules\generator-team\generators\app\utility.js:668

    callback(null, obj.value[0].id);
                                 ^

TypeError: Cannot read property 'id' of undefined

at Request._callback (C:\Program Files\nodejs\node_global\node_modules\generator-team\generators\app\utility.js:668:38)
at Request.self.callback (C:\Program Files\nodejs\node_global\node_modules\generator-team\node_modules\request\request.js:185:22)
at emitTwo (events.js:126:13)
at Request.emit (events.js:214:7)
at Request.<anonymous> (C:\Program Files\nodejs\node_global\node_modules\generator-team\node_modules\request\request.js:1161:10)
at emitOne (events.js:116:13)
at Request.emit (events.js:211:7)
at IncomingMessage.<anonymous> (C:\Program Files\nodejs\node_global\node_modules\generator-team\node_modules\request\request.js:1083:12)
at Object.onceWrapper (events.js:313:30)
at emitNone (events.js:111:20)

Hi @DarqueWarrior,
I love contributing to open source projects and this one is a great example of how we can make better tools for us and our users. I understand that this is a pet project that has now gained a lot of traction and interest by the community so I would like to suggest that we make it easier for people to contribute.

It would be great if we could add a Contributing.MD or expand the existing sections on the Readme.MD to explain how to download, develop and run on the local machine. This would help with people that don't have good experience working with local npm packages for example (like me...)

Thoughts?

How can we specify the http or https proxy setting for yo team?
The npm config for proxy and https-proxy does not seem to work

yo team hangs at "Getting Agent Queues" and then exits:

Seeing as VSTS and TFS are so versatile at dpeloying SQL Server project artefacts, it would be awesome to create these project types for yo team to simplify and get started with SQL Server DevOps pipelines using K8S/AKS, Azure SQL Database and onprem SQL Server, SSIS, SSRS, SSAS instances?

I am using yo team two submodules embedded in a powershell (due to compliance in a large finance company we need to run yo team in an agent with higher privileges)

yo team:project --applicationName $applicationName --tfs $organizationUrl --pat $azureDevOpsPersonalAccessToken
yo team:pipeline --applicationName $applicationName --tfs $organizationUrl --pat $azureDevOpsPersonalAccessToken --type $appType --queue $agentQueue --target $deployTarget --azureSubId $azureSubscriptionId --servicePrincipalId $servicePrincipleID --servicePrincipalKey $servicePrincipalKey --azureSub $azureSubscriptionName --tenantId $azureAdTenantId

What happens is that insertion of the vsrm to the url is broken with the azure devops. I have fixed it by hardforcing that url in the two calls to the releases api.

After that issue the team:pipeline freezes up if I supply the --queue parameter. If I omit it I can enter it in the provided menu (Hosted VS2017) and it works. Passing the value as param leads to a freeze. This problem is solved by downgrading node.js to version 8.

Hi @DarqueWarrior,

Is there a way we can automate creating the branch policies? I don't currently see a way to do that in the VSTS API. Would be an awesome feature to add to yo teams.

Thanks,
Joseph

When creating a .NET Core app, if the application name provided has a space in it, then namespaces in the application generated are invalid, leading to failed builds.

Hi,

could you please add support for 4.6 framework?