Team Foundation Server 2017 Update 3 版本資訊Team Foundation Server 2017 Update 3 Release Notes


|開發人員社群 |系統需求和相容性 |授權條款 |TFS DevOps Blog |Sha-1 雜湊 | |最新的 Visual Studio 2019 版本資訊|| Developer Community | System Requirements and Compatibility | License Terms | TFS DevOps Blog | SHA-1 Hashes | | Latest Visual Studio 2019 Releases Notes|


注意

這不是最新版的 Team Foundation Server。This is not the latest version of Team Foundation Server. 若要下載最新版本,請瀏覽 Team Foundation Server 2018 Update 3 的最新版本資訊To download the latest release, please visit the current release notes for Team Foundation Server 2018 Update 3. 若要變更此頁面的語言,請按一下頁尾的地球圖示,然後選取您想要的語言。You can change the language of this page by clicking the globe icon in the page footer and selecting your desired language.


本文提供 Team Foundation Server 2017 Update 3 的相關資訊。In this article, you will find information regarding Team Foundation Server 2017 Update 3. 按一下這個按鈕進行下載。Click the button to download.

Download Team Foundation Server 2017 Update 3.1

若要深入了解 Team Foundation Server 2017,請參閱 Team Foundation Server 的需求與相容性 (英文) 頁面。To learn more about Team Foundation Server 2017, see the Team Foundation Server Requirements and Compatibility page.

如需詳細資訊,請參閱 TFS 安裝頁面。Please see the TFS Install page for more information.

****

Release Notes Icon _ 發行日期:2019年9月10日*_ Release Date: September 10, 2019*

Team Foundation Server 2017 Update 3.1 Patch 8 的新功能詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 8

我們為 TFS 2017 Update 3.1 發行了安全性修補程式,其修正了下列 Bug。We have released a security patch for TFS 2017 Update 3.1 that fixes the following bug. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

****

Release Notes Icon _ 發行日期:2019年8月13日*_ Release Date: August 13, 2019*

Team Foundation Server 2017 Update 3.1 Patch 7 的新功能詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 7

我們針對 TFS 2017 Update 3.1 發行修補程式,它修正下列錯誤 (Bug)。We have released a patch for TFS 2017 Update 3.1 that fixes the following bug. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

  • Work Item Tracking Warehouse Sync 停止同步處理,因為發生下列錯誤:「TF221122:執行 Team 專案集合或 Team Foundation Server ATE 的工作 Work Item Tracking Warehouse Sync 時發生錯誤。The Work Item Tracking Warehouse Sync stops syncing with an error: "TF221122: An error occurred running job Work Item Tracking Warehouse Sync for team project collection or Team Foundation server ATE. ---> System.Data.SqlClient.SqlException:無法建立補償記錄。---> System.Data.SqlClient.SqlException: Cannot create compensating record. 遺漏歷程記錄資料。」Missing historic data."

Release Notes Icon 發行日期:2019 年 7 月 9 日Release Date: July 9, 2019

Team Foundation Server 2017 Update 3.1 Patch 6 的新功能詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 6

我們為 TFS 2017 Update 3.1 發行了安全性修補程式,其修正了下列 Bug。We have released a security patch for TFS 2017 Update 3.1 that fixes the following bug. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

  • CVE-2019-1072 :工作項目追蹤中的遠端程式碼執行弱點CVE-2019-1072: Remote code execution vulnerability in work item tracking

****

Release Notes Icon _ 發行日期:2019年5月14日*_ Release Date: May 14, 2019*

Team Foundation Server 2017 Update 3.1 Patch 5 的新功能詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 5

我們為 TFS 2017 Update 3.1 發行了安全性修補程式,其修正了下列 Bug。We have released a security patch for TFS 2017 Update 3.1 that fixes the following bugs. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

  • CVE-2019-0872 :Test Plans 中的跨網站指令碼 (XSS) 弱點CVE-2019-0872: Cross site scripting (XSS) vulnerability in the Test Plans
  • CVE-2019-0979 :使用者中樞中的跨網站指令碼 (XSS) 弱點CVE-2019-0979: Cross site scripting (XSS) vulnerability in the User hub

****

Release Notes Icon _ 發行日期:2019年4月9日*_ Release Date: April 9, 2019*

Team Foundation Server 2017 Update 3.1 Patch 4 中新功能的詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 4

我們為 TFS 2017 Update 3.1 發行了安全性修補程式,其修正了下列 Bug。We have released a security patch for TFS 2017 Update 3.1 that fixes the following bugs. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

  • CVE-2019-0866 :Pipelines 中的遠端程式碼執行弱點CVE-2019-0866: Remote code execution vulnerability in Pipelines
  • CVE-2019-0868 :Pipelines 中的跨網站指令碼 (XSS) 弱點CVE-2019-0868: Cross site scripting (XSS) vulnerability in Pipelines
  • CVE-2019-0870 :Pipelines 中的跨網站指令碼 (XSS) 弱點CVE-2019-0870: Cross site scripting (XSS) vulnerability in Pipelines
  • CVE-2019-0871 :Pipelines 中的跨網站指令碼 (XSS) 弱點CVE-2019-0871: Cross site scripting (XSS) vulnerability in Pipelines

****

Release Notes Icon _ 發行日期:2019年3月12日*_ Release Date: March 12, 2019*

Team Foundation Server 2017 Update 3.1 Patch 3 的新功能詳細資料Details of What's New in Team Foundation Server 2017 Update 3.1 Patch 3

我們為 TFS 2017 Update 3.1 發行了安全性修補程式,其修正了下列 Bug。We have released a security patch for TFS 2017 Update 3.1 that fixes the following bug. 如需詳細資訊,請參閱部落格文章Please see the blog post for more information.

  • CVE-2019-0777 :Pipelines 中的跨網站指令碼 (XSS) 弱點CVE-2019-0777: Cross site scripting (XSS) vulnerability in Pipelines

****

Release Notes Icon _ 發行日期:2018年2月 28 日*_ Release Date: February 28, 2018*

Team Foundation Server 2017 Update 3.1 的新功能詳細資訊Details of What's New in Team Foundation Server 2017 Update 3.1

此更新修正了可能的跨網站指令碼 (XSS) 與其他安全性弱點。This update fixes potential cross-site scripting (XSS) and other security vulnerabilities. 如需詳細資訊,請參閱部落格文章 (英文)。See the blog post for more information. 它是完整的升級,因此您可以直接升級至 TFS 2017 Update 3.1。It is a full upgrade, so you can upgrade directly to TFS 2017 Update 3.1.

****

Release Notes Icon _ 發行日期:2017年11月6日*_ Release Date: November 6, 2017*

Team Foundation Server 2017 Update 3 的新功能詳細資訊Details of What's New in Team Foundation Server 2017 Update 3

這是 Team Foundation Server 2017 的更新,包含自 Team Foundation Server 2017 Update 2 以來的 Bug 修正。This is an update for Team Foundation Server 2017 that includes bug fixes since Team Foundation Server 2017 Update 2.


工作Work

  • 當範本包含 > 127 的 ASCII 字元碼時,匯出結果不會有 WebLayout,而且會包含不正確的檔案名稱。Exporting a template with ASCII character code >127 does not have WebLayout and includes incorrect file names.
  • 面板和卡的設定無法處理工作項目類型重新命名。Board and Card Settings does not handle Work Item Type rename.
  • 重新排列的土耳其文工作流程看板卡應該按照堆疊順位。Kanban board card reordering in Turkish should be by stack rank.
  • REST API WorkItemSearchConditionalFaultIn 應該針對搜尋擲回 NotSupportedException。REST API WorkItemSearchConditionalFaultIn should throw NotSupportedException for Search.
  • WIT 的 StructureChangeNotification 事件未引發。StructureChangeNotification event not firing for WIT.
  • 當超過最大連結限制時,您可以新增詳細資訊的連結。Add link to more info when exceeding max links limit.
  • 將工作項目欄位資料移轉的執行計畫最佳化,以改進升級效能。Optimize work item field data migration execution plan to improve upgrade performance.
  • [指派至] 操作功能表應使用下拉式字串而不是顯示名稱,以明確指定。Assigned To context menu should use combo string instead of display name to disambiguate.

程式碼Code

  • Maven:現在會產生程式碼涵蓋範圍Maven: Code coverage will now be generated.
  • 在新的總管中,HTML 檔案不會再預設為預覽模式。HTML files will no longer default to Preview mode in the new Explorer.
  • 新增了檢視變更集時的捲軸We have added a scroll bar when viewing changesets.
  • 我們修正了 Web 中的垂直捲動功能 ([程式碼]-> [變更集] 與 [檔案]),現在可在 IE11 / Chrome 中使用We fixed the vertical scrolling in Web (both Code->Changesets as Files) will now work in IE 11/Chrome.
  • 捲動功能現在能在來源總管中使用 (IE/Edge)Scrolling now works in Source Explorer (IE/Edge).
  • 您現在可以針對已離開專案的使用者篩選變更集You can now filter changesets for users who have left the project.
  • 現在您可以選取檔案,然後選回左側樹狀中的根目錄,並維持在全螢幕模式中。You are now able to select a file, then select back in the root directory, of the left tree, and remain in full screen mode.
  • 若有大量存放庫,當搜尋 URL 超出預設支援的長度時,就不會再擲回例外狀況。The search URL will no longer throw an exception when it exceeds the defaulted supported length if there are a large number of repositories.
  • 若 Git 存放庫中沒有預設分支,就不再會設定檔案資料夾。File folders are no longer configured if there is no default branch in the Git Repository.
  • 延伸模組的安裝作業不會與先前的延伸模組解除安裝作業產生衝突。Extension installs will not conflict with the jobs of previous extension uninstall operations.
  • 我們已修正搜尋服務,現在即使作業失敗還是可以運作。We fixed Search and it now works despite job failures.
  • 若 Accountfaultin 作業執行超過一次,ReindexingStatus 將不再維持在 Inprogress 狀態下。ReindexingStatus will no longer remain in an Inprogress state if the Accountfaultin job is run more than once.
  • TFVC 搜耙將不再因版本控制 (VC) 權限問題而失敗。TFVC crawl will no longer fail due to version control (VC) permission issues.
  • 在日文組建升級至 TFS 2017 Update 2 之後,搜尋服務函式將不再失敗。The Search function will no longer fail post upgrade to TFS 2017 Update 2 in the Japanese build.
  • 搜尋服務函數不會再像從 TFS Update 1 升級至 TFS Update 2 時一樣失敗。The Search function will no longer fail as it did when upgrading from TFS Update 1 to TFS Update 2.
  • 作業結果訊息現在會提供更多關於編制索引的深入解析。The Job Result message will now give more insights into the indexing.
  • 我們已經降低修補作業失敗次數。We have reduced the Patch operation failure count.
  • 不論作業執行的時間限制為何,TimeBoxed Crawler 都會在至少一個批次編目。TimeBoxed Crawler will now crawl at least one batch irrespective of job execution time limit.
  • 我們已修正失敗檔案的修補作業 KPI,使其與搜尋服務的記錄一致。We fixed patch operation KPIs for failed files to be consistent with logs for Search.
  • 我們已改良 Git for Windows 中的 SSH 通訊協定版本支援。We improved the support for SSH protocol version in Git for Windows.

組建Build

  • 嘗試註冊組建代理程式時發生錯誤:驗證 -「沒有足夠的堆疊可安全地繼續執行此程式。」Error while attempting to register build agent: Authentication - "Insufficient stack to continue executing the program safely."
  • 更新 vsts-agent 以執行新版本的 GitUpdate vsts-agent to carry new version of git.
  • 啟用 NuGet 工具安裝程式工作,以在組建中加入 NuGet.exe 4.3.0,進而達成與 .NET 的相容性。Enable NuGet Tool Installer task in order to allow for NuGet.exe 4.3.0 to be included in builds for compatibility with .NET.
  • 排程的 XAML 組建 RequestedFor 欄位未設定。RequestedFor field of scheduled XAML build is not set.

版本Release

  • 從 TFS 2017 升級時,無法將 Azure 上的連線服務移轉到服務對服務端點。Upgrade from TFS 2017 failing migration of Azure-based connected service-to-service endpoint.

測試Test

  • 在 Win7 SP1 電腦上,部署測試代理程式工作有多個問題。Deploy Test Agent task has multiple issues on Win7-SP1 machine.
  • 錯誤的測試代理程式路徑不會登記為錯誤,而只會出現在偵錯中。If the Test Agent path is incorrect, it is not logged as error, but appears only in debug.
  • 當附件上傳失敗,測試回合/工作不應失敗。Test run/task should not fail if an attachment upload failed.
  • GetTestPlatform API 會根據設定,在探查目錄中尋找 testplatform.config 檔案。GetTestPlatform API will look for a testplatform.config file in the probing directory based on configuration.
  • 卸除 dbo.tbl_TestResult 上的索引以大幅改善升級效能。Drop indexes on dbo.tbl_TestResult to significantly improve upgrade performance.
  • 改善測試結果移轉維護步驟的效能,以大幅改善升級效能。Improve performance of test results migration servicing step to significantly improve upgrade performance.

報告Reporting

  • RDL 待執行工作報表現在已會顯示已刪工作的正確時間量。The RDL Burndown Reports now shows the correct amount of time for deleted tasks.

管理Administration

  • 使用者頁面公用 URL 應該與呼叫的 URL 相符,例如在牽涉到負載平衡器時。Users page Public URL should match the calling URL such as when a load balancer is involved.

已知問題Known Issues

無法在網頁中正確呈現工作項目表單Work item forms do not render correctly in the web

  • 問題:Issue:

    如果您為 Visual Studio 用戶端安裝了自訂控制項 (例如多重值控制項),但網頁用戶端未安裝,網頁中的工作項目表單將無法呈現。If you have a custom control, such as the multi-value control, installed for the Visual Studio client but not the web client, work item forms in the web fail to render.

  • 因應措施:Workaround:

    您需要更新為最新版的控制項。You will need to update to the latest version of your control. 此外還必須新增不含所 缺少之控制項元素的網頁配置。It is necessary to add a web layout that does not contain the missing control element. 您可以在 Custom Controls for TFS Work Item Tracking (TFS 工作項目追蹤的自訂控制項) 頁面上,找到 TFS 2017 Update 的最新多重值控制項。You can find the latest multi-value control for TFS 2017 Update on the Custom Controls for TFS Work Item Tracking page. 如需此版面配置的詳細資訊,請參閱 All FORM XML elements reference (TFS 2015) (所有 FORM XML 元素參考 (TFS 2015)) 頁面。For more information on the layout, see All FORM XML elements reference (TFS 2015) page.

查看 Team Foundation Server 2017 的客戶回報問題。See customer-reported issues reported for Team Foundation Server 2017.

The Developer Community Portal


意見反應與建議Feedback & Suggestions

我們很希望聽聽您的意見!We would love to hear from you! 您可以透過開發人員社群回報並追蹤問題,並在 Stack Overflow 上取得建議。You can report a problem and track it through Developer Community and get advice on Stack Overflow.


頁首
Top of Page