Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Import into VSTS bring none of the previous mappings #18

Open
swiontle23 opened this issue Apr 24, 2017 · 0 comments
Open

Import into VSTS bring none of the previous mappings #18

swiontle23 opened this issue Apr 24, 2017 · 0 comments

Comments

@swiontle23
Copy link

Installed product versions

  • Export/Import Buid Definition extension: Current version as of 4/24/2017

Description

None of the repository mappings get imported. One of my build definitions has 35 mappings and they are lost on every import.

Steps to recreate

  1. Create a new build definition with mappings in VSTS
  2. Export the build definition
  3. Run Microsofts TfsMigrator import command to create a new VSTS account using our collection.
  4. Re-import the build definition and it has no mappings.

Current behavior

Explain what it's doing and why it's wrong

Expected behavior

Explain what it should be doing after it's fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant