[TFS 2018] Build definition imported partially about vsteam HOT 8 CLOSED

The multiphase support in the rest api was done around 3.2 I believe.
So You probably need to set relevant VSTeamVersions item to higher than 3.2 (default is currently 3.0).
So even if your json file is of 4.0 structure, the default behavior will be to push to the 3.0 api, which does not have multiphase support and as a result “breaks” the build definition.

from vsteam.

This should be fixed now with PR #321 which allows also to target updates of servers @eduardohass.

from vsteam.

How large is the json file on disk? I wonder if there is a payload size I need to adjust in the post call or something.

from vsteam.

My files have 10kb.
I made a test with a release definition with 50kb and was successful.

from vsteam.

My next guess would be the format of the def has changed. I noticed that if I export a build def using API version 4.0 I can't then import it using API version 3.0. I would check the API used for the export is the same version used for the import.

from vsteam.

You can change the API version used. Run

help about_vsteam

To learn how to change the API version used.

from vsteam.

Thanks, @japj I was missing that point about multi-phase builds. I will work on a PR to update the version used in Azure DevOps.

from vsteam.

Is this still an issue?

from vsteam.