-
Notifications
You must be signed in to change notification settings - Fork 157
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
Get-VSTeamBuildDefinition should allow access to the build process #64
Comments
Are all the builds you want to patch the same structure just with different projects? If so you would export the JSON file. Then to patch you would update the JSON file and run Update-VSTeamBuildDefinition on each build def passing in the JSON file. If each are different then I would have to understand what your patch is doing. |
I may be already heading in this direction. Please check my PR. |
@DarqueWarrior We were trying to mostly do the same patch to each of the build definitions, but based on what was already there. I've now created a separate script that just calls the API's to take care of this. It is probably a one of thing anyway, so I'm good now. That being said, I believe there is a value in having access to the build process itself through VSTeam. I don't currently see a way of doing that, but it seems that @KaiWalter is already taking a stab at that. So as far as I'm concerned we can close this issue. |
@DarqueWarrior - I have no way to DM you right now. |
Currently it seems that Get-VSTeamBuildDefinition allows you to get metadata for a build definition, but does not allow access to the actual build process. Interestingly the Update-VSTeamBuildDefinition and Add-VSTeamBuildDefinition commands allow you to specify an input file to use as the build process.
I would like to use VSTeam to build a script to patch multiple build definitions at once, but it seems that that is not currently possible, given the above situation. Is this something to consider? I could take a stab at a PR, but I'm not sure if it fits the vision.
The text was updated successfully, but these errors were encountered: