WaelHamze / dyn365-ce-vsts-tasks

VSTS Extension for Dynamics 365 Customer Engagement
https://marketplace.visualstudio.com/items?itemName=WaelHamze.xrm-ci-framework-build-tasks
GNU General Public License v3.0
117 stars 56 forks source link

How do you Extract Solution to Source Control? #121

Closed SuperSaiyanHaris closed 4 years ago

SuperSaiyanHaris commented 4 years ago

Hi Wael,

Here is my extract solution step where my "Unpacked Files Folder" value is my branch in TFS: Build

The output shows that it's unpacking the files into the sources folder instead (This should be unpacking to my branch instead, right?): Ouput

Repository for the build: image

Let me know if you need any additional information. I am new to these processes so bare with me haha.

Thanks!!

SuperSaiyanHaris commented 4 years ago

Hi Wael,

I have been able to successfully get my solution files into source control so ignore my above question. However, I am wondering if your tools have the capability to add new items to source control? When I do a check-in, I can see all my existing files changes, but for example, if a new entity was created and now the "Entities" folder has "New Entity" folder in it that needs to get source controlled, do I always have to manually add new items?

Thanks,

mattp65 commented 4 years ago

Solution Packager has no knowledge of your source control, it just interacts with the local file system of the server executing it. You need to add a step to do the checkin from that workspace in the local folder to your source system. It is no different than if you run Solution Packager on you own machine, you then have to do something to get it into Source Control (Git or VSTS or whatever).

WaelHamze commented 4 years ago

@SuperSaiyanHaris as @mattp65 suggested the task doesn't put a dependency on a specific source control system. You can use Git commands to achieve this.