how to check out all the Assembly info files using pattern recursively

[harishchepuri]

how to check out all the Assembly info files using pattern recursively

[jessehouwing]

It follows the same pattern as tf.exe.

Though you shouldn't have to check them out, the 2.x agent uses local workspaces. If you're still on agent 1.x it's really really time to upgrade.

I suspect the pattern is assembly.cs and then check the recursive checkbox.

On Sat, 25 Aug 2018, 16:41 harishchepuri, notifications@github.com wrote:

how to check out all the Assembly info files using pattern recursively

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS1jfAUjw5yrBHJyQUw6lIPXSVn7Zks5uUWIlgaJpZM4WMaMv .

[harishchepuri]

yes you are correct my version is showing as 1.* but recently after 2.0 released anyway how to update to latest agent

[jessehouwing]

Just uninstall the 1.x agent and then install the 2.x agent. Your tfs/vsts service should offer the download link to its latest supported version.

On Sat, 25 Aug 2018, 17:26 harishchepuri, notifications@github.com wrote:

yes you are correct by version is showing as 1.* but recently after 2.0 released anyway how to update to latest agent

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67#issuecomment-415976777, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS_WWlEBrG1vqa-cGnUiAlyVJqmqMks5uUWyRgaJpZM4WMaMv .

[harishchepuri]

I uninstalled and installed still its showing as 1.0

[jessehouwing]

Task or agent?

On Sat, 25 Aug 2018, 17:33 harishchepuri, notifications@github.com wrote:

I uninstalled and installed still its showing as 1.0

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67#issuecomment-415977266, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS1LM_y44C8FZBrzGTY4MiJfTrA3bks5uUW46gaJpZM4WMaMv .

[harishchepuri]

Task

[jessehouwing]

Checkout is only needed when using the 1.x agent and a server workspace. And is officially not even supported

In all other cases, just overwrite the files.

On Sat, 25 Aug 2018, 17:39 harishchepuri, notifications@github.com wrote:

Task

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67#issuecomment-415977672, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS6qhdlByD8pSuv9USk15qKAqvMrYks5uUW-pgaJpZM4WMaMv .

[harishchepuri]

what is this 2.x agent

[jessehouwing]

Ok, I'll need a better report.

What are you using?

• TFS, which version
• VSTS

What agent are you using?

• VSTS hosted agent, which pool?
• Self hosted agent, which version (check the agent queue)

What is the default workspace setting of the

• Team Project
• Team Project Collection

In most cases you won't need to use the Checkout task. The checkout task is only needed when you are using:

• TFS 2015
• VSTS Agent 1.83 ~ 1.95
• Team Project Collection default setting

https://docs.microsoft.com/en-us/vsts/repos/tfvc/decide-between-using-local-server-workspace?view=vsts#manage-project-collection-workspace-settings-for-your-team

In all other cases the build agent will create a local workspace and using that the files are automatically checked out.

If you're still using this configuration it's highly recommended to upgrade to a more recent version of TFS, in which case you'll be able to use the 2.x build agent and won't need to use the checkout task either.

On Sat, 25 Aug 2018, 17:56 harishchepuri, notifications@github.com wrote:

what is this 2.x agent

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67#issuecomment-415978668, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS9e63HlZQHJhGmx06j-aGCPWsLLXks5uUXOUgaJpZM4WMaMv .

[harishchepuri]

thank you for your reply. please find my comments below

1) TFS 2018 2)VSTS Agent 3)Team Project Collection default setting

actually I will explain why I am using checkout and check-in we are updating the assembly info class with assembly version and date so that dev team wont get conflicts Please find my build definition flow 1) Get the source from the server 2)Update the assembly info class 3)checkout only assembly info classes 4)build the solution 5)Check-in the updated assembly info class

my solution file contains 20 projects each one has one assembly info class so that I given 20 assembly info paths but when I am saving build I am getting error like folder limit length so I used folder path and kept as recursive full but when check-in task is check-in all the files even though no changes in other CS files except assembly info

[jessehouwing]

I'd try one if the following:

• multiple checkout tasks that check out a set of files each. Then one checkin task.
  • don't use the checkout task, and use a checkin task configured to detect changes automatically

I suspect I may be able to extend the length if the input box... But I'm not sure I want to. The checkout task is really a temporary solution for a few people using tfs 2015. On the vsts agent it should be a no-op. And won't actually lock anything.

On Mon, 27 Aug 2018, 06:19 harishchepuri, notifications@github.com wrote:

thank you for your reply. please find my comments below

1. TFS 2018 2)VSTS Agent 3)Team Project Collection default setting

actually I will explain why I am using checkout and check-in we are updating the assembly info class with assembly version and date so that dev team wont get conflicts Please find my build definition flow

1. Get the source from the server 2)Update the assembly info class 3)checkout only assembly info classes 4)build the solution 5)Check-in the updated assembly info class

my solution file contains 20 projects each one has one assembly info class so that I given 20 assembly info paths but when I am saving build I am getting error like folder limit length so I used folder path and kept as recursive full but when check-in task is check-in all the files even though no changes in other CS files except assembly info

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/jessehouwing/vsts-tfvc-tasks/issues/67#issuecomment-416110025, or mute the thread https://github.com/notifications/unsubscribe-auth/AD-uS2wjBaYEX-10bTfAej9nlSf40nRtks5uU3NWgaJpZM4WMaMv .

[harishchepuri]

i updated the assembly info class and when i am trying to checkin it showing message no changes to checkin ,i cross checked the build working folder and i am able to see changes , any idea about this why its showing above message