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

Added cmdlet Test-VSTeamYamlPipelines for testing YAML pipeline code #272

Merged
merged 21 commits into from
Mar 11, 2020
Merged

Added cmdlet Test-VSTeamYamlPipelines for testing YAML pipeline code #272

merged 21 commits into from
Mar 11, 2020

Conversation

SebastianSchuetze
Copy link
Collaborator

@SebastianSchuetze SebastianSchuetze commented Feb 26, 2020

PR Summary

added a new cmdlet for a new API that was released the last sprint.

https://docs.microsoft.com/en-us/azure/devops/release-notes/2020/sprint-165-update#azure-pipelines-1

I still need to add some documentation first and change the changelog.

PR Checklist

@tomkerkhove
Copy link

Do we need 'VSTeam' prefix? For consistency reasons?

@SebastianSchuetze
Copy link
Collaborator Author

SebastianSchuetze commented Feb 28, 2020

Do we need 'VSTeam' prefix? For consistency reasons?

@tomkerkhove, The whole module is called VSTeam and every cmdlet has it as well. Which is consistent with the e.g. AzureAD, Az, AzureRM modules. This is how you prevent also conflicts with other modules which could be loaded as well.
You can see it like a namespace.

@SebastianSchuetze
Copy link
Collaborator Author

SebastianSchuetze commented Feb 28, 2020

@JustinGrote do you see any useful parameters that might make sense to add?

@tomkerkhove
Copy link

Sounds good to me!

@DarqueWarrior DarqueWarrior merged commit 6e505d1 into MethodsAndPractices:master Mar 11, 2020
@SebastianSchuetze SebastianSchuetze deleted the feature/Test-VSTeamYamlPipeline branch March 11, 2020 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants