Manage deployment versions with TFS without devops procedure
We are using the TFS for managing our tasks/bugs in Agile methodology.
Currently we don't have DevOps to handle CI/CD procedures, we just manually upload the publish to our private server after our QA made his tests and approved the release branch.
My question is, since in agile development i can deploy to production every time my project manager asks me to (since the feature he asked for is ready and made it with the tests), how can i use the TFS to "grab" all those tasks/features/bugs that went to production and show her what is new on production?
My first choice was to use the Tags to tag items as "1.1.2". But then i thought that someone will still need to mark it at some point as "1.1.2" so its again a manually thing. And who will it be? The project manager? clearly not. The developer? what if we decided to hold his latest feature and go with other one to the closer version? And finally, me? So it comes back to me as the team leader. But what is my best tool here?
Example, one of my team members finished feature F1, bugs B1 and B2 and he checks them in with their associated PBI. Other team member finishes features F2 and F3 (very productive of him). Both of them merge it to the release branch and later i have merged it to production branch. What is my option at this point to answer the question "What's new in our latest version?" without going to my team members, the TFS history, the TFS current sprint (and maybe older ones)?
Thanks!
Automate your build and deployment process. As long as developers are associating work items with commits, your releases will automatically be able to display that information and even generate an email.
You didn't specify what version of TFS you're using, but this has been a feature since TFS 2015 Update 2.
- How TFS version tracker will track the .PBL files of PowerBuilder code, does it track events, functions of .PBL files?
- Sonarqube TFS task returning error (401) Unauthorized on one project but not others
- Why does it say "Project with that name already opened in the solution"?
- How to get project on the source control in visual studio
- Team Explorer Everywhere Command Line Client workflow map validation errors
- TFS - An item with the same key has already been added
- How to pull source codes from TFS for building images in openshift pipeline
- Visual Studio / Nuget puts files in the wrong place
- CodeLens not showing references
- TFS 2017 Git API - Get Tag By Name
- How to branch my Visual Studio Online (TFS) Solution?
- No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again
- WorkItem Creation Transaction Rollback
- Opening Source Control Explorer in Visual Studio 2022
- Remove project from visual studio solution
- Folders created in visual studio solution under solution explorer not appearing in source control explorer
- How to force Visual Studio to use the TFS source control provider and not GIT provider
- Error 500 while creating Azure DevOps server connector in Microsoft teams
- Get Visual Studio to run a T4 Template on every build
- How to Retrieve the Triggering Pipeline's runName in a YAML Release Pipeline
- 401 - Unauthorized: Access is denied due to invalid credentials when Trying to access the TFS API by postamn
- How to get a branch name for a dedicated changeset number via PowerShell
- TFS build write message to summary
- Exception setting "CursorPosition": "The handle is invalid." when running pipeline task using PowerShell Core
- Azure DevOps. Can't trigger a pipeline in Repo A when a commit is done in repo B
- TFS and referenced DLLs
- How to Migrate TFVS project to Azure Git Repos from different Organization
- TFS source control - new files not automatically detected as pending changes
- Azure DevOps API Authentication
- How can we make a Work Item Creator automatically a Follower?