Closed srivatsamarichi closed 8 years ago
Hi Srivatsa, Thanks for letting me know. Unfortunately, I am getting a completely different error (repository.id is null) while importing your json. Can you please let me know if this is correct JSON? Regarding the error, can you let me know,
I will try to create the definition based on your response and try to replicate the issue.
Hi Utkarsh, Sorry for the delay in response as i was on business travel. Please find the inline replies for the same-
When i run the Powershell script, it will ask the parameters like vsts account,PAT,build definition path, local working folder.So this powershell will automatically download the source code for my local repo and will upload the existing JSON files that i'm mapping to. I thought of doing it through the extension which was available in the VS Marketplace which would serve my purpose but i was failed miserably. Let me know if you need anything else :-) BTW, great extension though! Thanks,Srivatsa
On Tuesday, 19 July 2016 2:13 AM, Utkarsh Shigihalli <notifications@github.com> wrote:
Hi Srivatsa, Thanks for letting me know. Unfortunately, I am getting a completely different error (repository.id is null) while importing your json. Can you please let me know if this is correct JSON? Regarding the error, can you let me know,
@SrivatsaMarichi Sorry for coming back late on this one. Been very busy with work and there were few technical challenges for export/import b/w cross version control (for ex: git <=> tfvc). I have a question, in your sample file attached above, I see a task named Version Assemblies using AssemblyInfo.*
. Is this a custom task? Installed via extension? If yes, can you please provide me extension URL?
@SrivatsaMarichi Please try the latest version and let me know if you still have the same issue.
Installed product versions
Description
I am trying to import an existing build definition template (which is a json file) to one of my VSTS account and i am facing the above mentioned Exception
new 2.txt