Azure DevOps - TFVC or Git

(0) Share

Report

Posted on by Yuji

4,131

Hi,

I know it is recommended to use TFVC type project when we create Azure DevOps project, but what exactly the reason that we could not use Git?

Thanks,

I have the same question (0)

All responses (6)

Answers (2)

Blue Wang Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Yuji,

Microsoft does not support Azure Dev Ops (VSTS) automated builds for git repositories by default.

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report
Copy link

Link copied!

Is it easy to move the Azure DevOps project from Git to TFVC?

Was this reply helpful? Yes No
Sergei Minozhenko 23,095 on at

Like (0)

Report
Copy link

Link copied!

Hi Yuji,

Here is answer about Git to TFVC migration stackoverflow.com/.../convert-git-repository-to-tfvc-version-control.

Was this reply helpful? Yes No
Verified answer

Joris dG 17,780 on at

Like (2)

Report
Copy link

Link copied!

Although we don't officially support it, there are plenty of people using Git. I would say, if you are familiar with Git as well as understand the structure of the X++ source (packages/descriptors etc) and all that stuff you should be able to get this done. The problem is largely around swapping branches, and/or requiring maintaining a big gitignore file.

You will need a TFVC repo (can be empty) to be able to _deploy_ a build VM, but the build VM can build from a Git repo just fine if the folder structure matches the TFVC folder (metadata/project subfolder).

See msdyn365fo.wordpress.com/.../

and www.atomicax.com/.../giting-started-git-d365fo-and-other-puns

Was this reply helpful? Yes No
Yuji 4,131 on at

Like (0)

Report
Copy link

Link copied!

Thanks Joris,

One more question, the recommended folder structure (metadata/projects sub folder), we have to follow this otherwise the build activity doesn't work?

Was this reply helpful? Yes No
Verified answer

Joris dG 17,780 on at

Like (0)

Report
Copy link

Link copied!

Correct. The build definition assumes you have your code in a /metadata/ folder and your projects in a /projects/ sub folder.

You can certainly change the scripts on the build VM to remove this assumption, but every time you take an update you will have to redo that script change.

We will have the new build system in preview and that will work however you want, so if you can live with it for now it will certainly become easier soon enough.

Was this reply helpful? Yes No