2. 設定及個人化助理 [GA]
啟用 API - 這項操作由 Bumble 管理員執行。請注意，這項操作不適用於參與者，因為參與者可能無法存取 Google Cloud 控制台。
需要將此項目新增為雲端管理員完成研討會的先決條件
設定個人化功能
「Consumer Software & Mobile App Development」不在下拉式選單中，因此他們需要選取「自訂」，然後新增這項
然後關閉該彈出式視窗
3. 設定資料連接器 [正式發布版]
這項操作是由 Gemini Enterprise 管理員執行，而非參與者。因此請將這項工具列為研討會的先決條件。
4. 與 Jira 連接器的基本互動 [正式發布版]
首先，每位參與者都必須授權連接器，才能使用 Jira 和 GitHub 連接器。以下是相關螢幕截圖：
image-1-jira-authozie.png
image-2-jira-authoziation-page.png
image-3-after-jira-authoziation.png
對 GitHub 執行相同操作
使用 Jira 或 GitHub 連接器時，也請停用 Google 搜尋
image-4-disable-google-search.png
1. 找出 Jira 專案金鑰 - 說明如何開啟對話視窗來詢問 Gemini，下方為參考螢幕截圖
Image-5-jira-list-projects.png
其他測試也請照此辦理，例如建立工作、留言、更新狀態等。並相應更新相關螢幕截圖
image-6-jira-create-projects-1.png
image-7-jira-create-projects-2.png
image-8-jira-create-projects-3.png
image-9-jira-comment-1.png
image-10-jira-comment-2.png
image-11-jira-comment-3.png
image-12-jira-status-1.png
image-13-jira-status-2.png
image-14-jira-status-3.png
5. 與 GitHub 連接器進行基本互動 [正式版]
如要提交待辦事項清單，您必須知道存放區名稱。因此，請使用如下的提示來取得存放區名稱。
執行這項作業前，請先請參與者停用其他連接器，只保留 GitHub。
針對所有測試取得相關圖片，並相應新增。以下是螢幕截圖檔案名稱。
image-15-github-enable-1.png
image-16-github-list-repo-2.png
image-17-github-list-commit-3.png
image-18-github-list-pull-request-4.png
image-19-github-list-pull-request-summary-5.png
6. 交叉參照執行說明文件 [正式發布]
在「上傳需求文件」步驟中，應先完成步驟 2「上傳名為 requirements.txt 的檔案，並在其中加入下列內容」，這樣參與者就能在筆電中建立檔案，並將檔案上傳。如要在 Mac 上建立 .txt 檔案，請使用內建的 TextEdit 應用程式。開啟 TextEdit，前往頂端選單，依序點選「格式」>「製作純文字」。輸入文字、依序點選「檔案」>「儲存」、為檔案命名 (請務必以 .txt 結尾)、選擇儲存位置，然後按一下。為其他筆電提供類似的指示
此外，「在 Gemini Enterprise 對話介面中，按一下 + (加號) 圖示，或拖曳檔案以上傳。」目前不適用
建立需求文字後，開啟新的對話視窗，停用其他連結器並只啟用 Jira，然後使用 Gemini 建立範例資料，再執行分析。這時，使用者需要將 TXT 檔案上傳至 Gemini 應用程式。請參閱下方的測試螢幕截圖，這些螢幕截圖的檔案名稱依序排列。
image-20-jira-req-txt-1.png
使用 Gemini 生成範例資料的圖片
image-21-jira-create-ticket-2.png
image-22-jira-create-ticket-confirmation-3.png
image-23-jira-create-ticket-done-status-confirmation-4.png
image-24-jira-create-ticket-confirmation-5.png
image-25-jira-create-ticket-inprogress-status-confirmation-6.png
image-26-jira-create-ticket-created-6.png
image-27-jira-create-tinjira-portal-7.png
執行分析的圖片
image-28-jira-run-analysis-1.png
image-29-jira-run-analysis-output-2.png
注意「按一下回覆中提供的引用內容，即可確認 Gemini 參照的是檔案或 Jira 票證的哪個部分。」但我實際上看不到引用內容
7. 使用 NotebookLM 分析衝刺待辦事項 [正式版]
同樣地，請先建立 txt 檔案，然後提供相關指示，再按一下「建立新筆記本」。然後上傳名為 retro.txt 的檔案，其中包含以下模擬附註：
請提供生成洞察資料的指令，說明要點選的內容。
以下是這些螢幕截圖的圖片檔
image-30-notebook-lm-output.png
image-31-notebook-lm-mindmap.png
8. 深入研究市場趨勢 [公開測試版]
查看實際測試執行的螢幕截圖，並更新說明 (如有缺漏)。螢幕截圖的檔案名稱。並說明這些作業需要一些時間才能完成，因此請觸發作業，然後繼續下一個實驗室，直到作業完成為止。此外，請提供報表中的審查內容詳細資料，並審查
deep-research-1.png
deep-research-2.png
deep-research-3.png
9. 運用點子生成功能發想創意 [公開測試版]
查看實際測試執行的螢幕截圖，並更新說明 (如有缺漏)。螢幕截圖的檔案名稱。並說明這些作業需要一些時間才能完成，因此請觸發作業，然後繼續下一個實驗室，直到作業完成為止。此外，請提供報表中的審查內容詳細資料，並審查
idea-agent-1
idea-agent-2
idea-agent-3
idea-agent-4
idea-agent-5
10. 建立多步驟 Scrum Master 助理 [公開測試版]
選取「新增代理」時，請先點選「聊天代理」，因為「工作流程代理」的「新增代理」下方有預覽選項，本節不會介紹。
請參閱 scrum-master-1.png 圖片
如要重新命名代理，請按一下中間的方塊開啟側邊面板，請參閱圖片 scrum-master-3.png 和 scrum-master-4.png
請參閱圖片，瞭解提供提示的下一個步驟 - scrum-master-5.png
在步驟 3 中，請提供下列指令：這會建立啟用 Google 搜尋的代理程式，並將代理程式重新命名為「Lead Scrum Master」，請參閱圖片 scrum-master-6.png。因此，我們將步驟 2 移除，將代理重新命名為「Bumble-Lead-Scrum-Master」，因為提示會重新命名，但請務必將其命名為「Lead Scrum Master」。
Also inthe prompt ask it to use only jira and github connector not use google search.
此外，請將其餘指令中的「Bumble-Lead-Scrum-Master」替換為目前的代理程式名稱
新增專用子代理
步驟 1
在步驟 4 中，我們已搜尋專案金鑰。Basic Interactions with Jira Connector [GA] lab step 1
取消勾選 Google 搜尋，只保留 Jira
請參閱下圖，並確保相應更新操作說明
scrum-master-7.png
Scrum-master-8.png
步驟 2
在操作說明中提及先前在步驟 5 中搜尋的存放區名稱。與 GitHub 連接器進行基本互動 [正式版] 步驟 1
取消勾選 Google 搜尋，只保留 GitHub
請參閱下圖，並確保相應更新操作說明
scrum-master-9.png
scrum-master-10.png
scrum-master-11.png
這個提示實際上是在搜尋公開的 GitHub，並取得「Generate the high-priority update for the Bumble project for the past 24 hours.」(為 Bumble 專案產生過去 24 小時的高優先順序更新) 的結果，這完全不正確。代理程式只能從我提供的 Jira 專案和 GitHub 存放區尋找資料。不確定原因。
請參考這張螢幕截圖，瞭解我得到的輸出內容 - scrum-master-12.png。以下為實際輸出內容
請務必正確更新指令，確保只搜尋代理程式中設定的 Jira 專案和 GitHub 報表
Generate the high-priority update for the Bumble project for the past 24 hours.
Response complete
Gemini replied
Here is the high-priority daily update for the Bumble project ecosystem over the past 24 hours. [107, 109, 928, 934]
-
🚀 Overall Progress Summary
The past 24 hours saw significant progress in integrating Google’s Bumble Bluetooth stack across downstream tools, notably introducing native Windows support for NXBT
and adding optional BLE pairing transports to smpclient [107]. Additionally, core refactoring in Bumble's AVDTP (Audio/Video Distribution) layers has successfully eliminated resource-locking bugs [928]. Meanwhile, the community is actively tackling high-priority Classic Bluetooth pairing failures and Windows boot-up driver issues [59, 934].
-
✨ Key Achievements & Code Progress (GitHub)
Repository / Project
Contribution
Details
intercreate/smpclient
BLE Transport with Pairing (PR #107)
Added an optional bumble extra (smpclient[bumble]) providing SMPBumbleTransport [107]. This BLE transport drives external HCI USB controllers, supporting secure scanning, pairing PIN flows, and stored LTK encryption [107].
google/bumble
AVDTP In-Use Management (PR #928)
Merged! Avoids explicit stream in_use flag management by delegating to a dynamic property checking if stream state is IDLE [928]. This resolves previous edge-case resource leaks [923].
typenoob/nxbt
Native Windows Support (Issue #4)
Announced a major integration with Bumble enabling native Windows support for NXBT controllers via hci-socket and usb (WinUSB) transports
.
badoo/codeisok
Security Hardening (PR #109)
Enabled the secure flag for authentication cookies in the Login controller to prevent unencrypted session token transmission [109].
-
⚠️ Current Blockers & High-Priority Issues
While no tracking issues were found in Jira for "Bumble", the following high-priority issues are currently impeding progress in the GitHub ecosystem:
Classic Bluetooth Pairing Failures (Issue #59 - kindle-hid-passthrough) [59]
Status: Active / Investigation [59]
Impact: Classic-only Bluetooth HID devices (such as the Logitech K811 keyboard) fail during Simple Secure Pairing (SSP) with an AUTHENTICATION_FAILURE_ERROR (0x05) [59]. Bumble appears to bypass the user pairing delegate entirely [59].
Next Steps: Testing a speculative fix on feature/brcm-bt-support that relaxes pairing config constraints for BR/EDR [59].
Windows Startup Power-On Failures (Issue #934 - google/bumble) [934]
Status: Open [934]
Impact: Bluetooth USB dongles fail to power on during the very first boot on Windows systems [934]. The Intel driver receives a disallowed error (HCI_COMMAND_DISALLOWED_ERROR) during the initial HCI_RESET_COMMAND [934].
-
Would you like me to draft any replies to these active issues or prepare a Confluence summary document of the Windows workarounds?
give me the link for this repo intercreate/smpclient
Response complete
Gemini replied
The link for the intercreate/smpclient repository is:
👉 https://github.com/intercreate/smpclient
intercreate/smpclient repo is not in my repo in mumanoha/gemini-code-review-agent-demo. intercreate/smpclient is a public repo why are you getting me all the public repo
Response complete
Gemini replied
I retrieved results from public repositories because the search query for "Bumble" was executed globally across all of GitHub rather than being restricted to your specific repository (mumanoha/gemini-code-review-agent-demo).
When I initially searched your internal Jira projects and repositories for the project "Bumble", it returned no matches. To ensure I didn't miss any relevant information, my search query broadened its scope to look for any active issues or pull requests containing the keyword "Bumble" globally, which pulled in these public repositories (like Google's bumble library and intercreate/smpclient).
-
🔍 Filtering to Your Specific Repository
If "Bumble" is a branch, a specific folder, or a topic within your repository, I can narrow down the search.
Would you like me to run a targeted analysis specifically on mumanoha/gemini-code-review-agent-demo for any updates or commits made in the past 24 hours instead?
如果我使用「Generate the high-priority update for the my projects for the past 24 hours.」提示，會得到以下輸出內容：
請參閱圖片 scrum-master-13.png
Generate the high-priority update for the my projects for the past 24 hours.
Response complete
Gemini replied
📊 Daily Project Status Report (Past 24 Hours)
-
🚀 Overall Progress Overview
Currently, the projects are focused on resolving critical infrastructure blockers on Google Cloud Platform while maintaining a steady baseline on application services. While there has been no new code merged or committed in the last 24 hours, the active development continues to center around service integration, and the infrastructure pipeline is currently held back by two newly updated high-priority Jira issues
.
-
🛠️ Code Progress & Achievements (GitHub)
There are no new commits or merged pull requests to report for the past 24 hours. The primary active work-in-progress remains:
Repository / PR
Status
Description
mumanoha/gemini-code-review-agent-demo PR #1: feat: Add menu-service application
🟡 Open
This pull request introduces the core menu-service application to the repository.
-
⚠️ Blockers & High-Priority Issues (Jira)
The following high-priority infrastructure issues were updated in the past 24 hours under the ge-bugs project and require immediate attention to prevent further deployment delays on the GCP Migration Strategy
:
Key
Priority
Status
Summary
Impact
GB-5
🔴 High
To Do
IAM permission shadowing in VPC
Conflicting IAM policies between the VPC and GKE cluster are causing intermittent permission denied errors for active services
.
GB-4
🔴 High
To Do
GKE node pool auto-scaling timeout
The GKE node pool is failing to auto-scale automatically, leading to pod scheduling failures under load
.
-
Let me know if you would like me to help assign these blockers or draft a follow-up message to the infrastructure team!
此外，也不確定是否要在根代理中新增連接器。我移除了根代理程式中的連接器，並進行測試，輸出內容如下。哪種設定正確？我不確定，請您決定正確的設定
請參閱圖片 - scrum-master-14.png
Generate the high-priority update for the my projects for the past 24 hours.
Response complete
Gemini replied
High-Priority Update: Project GB (ge-bugs)
Here is the summary of P0/P1 (Highest/High priority) issues and blocked tickets in Project GB (ge-bugs) along with their current impact:
1. P0/P1 Issues (High Priority)
GB-4: GKE node pool auto-scaling timeout
Priority: High (P1)
Impact: The GKE node pool is failing to auto-scale dynamically under load. This results directly in pod scheduling failures, threatening application reliability and performance during high traffic
.
GB-5: IAM permission shadowing in VPC
Priority: High (P1)
Impact: Conflicting IAM policies between the VPC and the GKE cluster are causing intermittent "permission denied" errors for services, leading to unstable internal communication
.
2. Blocked Tickets
GB-7: Fix database latency issues
Priority: Medium
Status: Blocked
Impact: Progress on resolving database latency is halted. The ticket is currently blocked while waiting for the infrastructure team to increase IOPS
.
-
I will now hand control back to the root agent to synthesize this update into your unified daily report. Let's make sure this progress is tracked.
I have checked the open Pull Requests in the mumanoha/gemini-code-review-agent-demo repository:
Open Pull Requests:
PR #1: feat: Add menu-service application
State: Open
Review Status: There is currently one review submitted by gemini-code-assist[bot], which has a status of COMMENTED (not CHANGES_REQUESTED). The reviewer provided general code quality, testing, and dependency cleanup suggestions but did not block the PR with an explicit changes-requested status.
Therefore, there are no Pull Requests currently in the "Changes Requested" state.
I will now transfer control back to the root_agent to compile the complete update. Here is your unified daily report for the past 24 hours, highlighting the high-priority Jira blockers and active code progress on GitHub.
I, Gemini Enterprise, have analyzed your active projects and compiled the most critical updates to keep you and your team aligned.
-
🚨 High-Priority Jira Issues & Blockers
There are currently two high-priority bugs active in Project GB (ge-bugs), along with one blocked issue that requires infrastructure intervention.
Issue
Priority
Status
Description & Impact
GB-4: GKE node pool auto-scaling timeout
High
To Do
The GKE node pool is failing to auto-scale under load, resulting in active pod scheduling failures.
GB-5: IAM permission shadowing in VPC
High
To Do
Conflicting IAM policies between the VPC and GKE cluster are causing intermittent service permission errors.
GB-7: Fix database latency issues
Medium
🛑 Blocked
Progress is currently halted. The team is waiting on the infrastructure team to increase IOPS.
-
💻 GitHub Code Progress
Active progress continues on the gemini-code-review-agent-demo repository with one open pull request. There are currently no PRs blocked under a "Changes Requested" status.
PR # & Title
State
Review Status
Key Highlights
#1: feat: Add menu-service application
Open
Commented
Adds the menu-service Quarkus application. gemini-code-assist[bot] provided recommendations to clean up pom.xml, improve JPA mapping, utilize Panache's active record pattern, and expand test coverage.
-
Would you like me to help you draft a follow-up message to the infrastructure team to expedite the IOPS increase for GB-7, or would you like to dive deeper into any of these updates?
11. 建構資源影響分析器代理程式 [公開測試版]
選取「新增代理」時，請先點選「聊天機器人代理」，因為「新增代理」下方有「工作流程代理」的預覽選項，但我們不會在本節中介紹。
請參閱 scrum-master-1.png 圖片
請改為依序點選「建立新代理程式」>「繼續前往製作工具」。我們直接在對話中提供提示。請參閱這張螢幕截圖：resource-impact-1.png
代理程式建立專案後，請取消勾選 Google 連接器，然後按一下「預覽」測試提示「Team member ‘Muthu' is out for 3 days. 會有什麼影響？」
請參閱圖片，並確保相應更新說明
resource-impact-2.png 和 resource-impact-3.png
測試完畢後，按一下「建立」即可發布代理程式
12. 進階：使用 ADK 建構及部署 [公開測試版]
我已為這些步驟截圖，請查看螢幕截圖，確認說明是否正確，並更新每個步驟的螢幕截圖，確保清楚明瞭
步驟 1：設定環境
agent-cli-1.png
步驟 2：驗證及設定
agent-cli-2.png
agent-cli-3.png - this steps a long time
agent-cli-4.png -
在操作說明中提及 CLI 會要求執行指令的權限，並選取「允許一次」
選項 B：使用 Gemini CLI (自然語言)
請參閱圖片，根據主控台實際發生的情況正確更新操作說明。視需要使用這些螢幕截圖更新程式碼研究室，並提供相關說明
待審查的圖片 - agent-cli-5.png 至 agent-cli-9.png
以下是 CLI 中的輸出內容
我已使用 Agent Development Kit (ADK) 為您建構 Bumble-Ops-Assistant 代理。
1. 代理程式實作
代理程式位於 bumble-ops-assistant/app/agent.py。其中包含 check_build_health 工具，可為任何環境傳回硬式編碼的「GREEN」狀態。
1 def check\_build\_health(environment: str) \-\> str:
2 """Checks the build health for a given environment.
3
4 Args:
5 environment: The environment to check (e.g., 'prod', 'staging').
6
7 Returns:
8 The health status of the build.
9 """
10 return "GREEN"
11
12 root_agent = Agent(
13 name="Bumble_Ops_Assistant",
14 # ...
15 instruction="You are Bumble-Ops-Assistant, an operations assistant. 您可以查看正式版和測試版環境的建構健康狀態。
16 tools=[check_build_health],
17 )
2. 冒煙測試
我執行了兩種冒煙測試：
* 單元測試：我在 bumble-ops-assistant/tests/unit/test_health_tool.py 中建立並執行單元測試，直接驗證工具的邏輯。
* Result: 2 passed in 3.03s
* Evaluation Smoke Test: I scaffolded a simple evaluation set in bumble-ops-assistant/tests/eval/evalsets/smoke_test.evalset.json to test the agent's interaction.
* 注意：評估執行作業發生 PERMISSION_DENIED 錯誤，是因為 aiplatform.googleapis.com API 未在 cloudshell-gca 專案中啟用，且我沒有權限啟用該 API。
agent-cli-10.png - shows when clicked on open editor and ask the participants to review the files to see what agent cli created, and give explanation on each of the files create by agent cli refer to the documentation for details
Playground testing - provide those steps before deploy and publish.
請參閱這些圖片，瞭解測試方式並據此建立操作說明
圖片 - agent-cli-11.png 至 agent-cli-15.png
我嘗試要求 Agent CLI 建立並測試 Playground，但遇到問題。
找不到工作階段：f681747b-c55d-42d6-9324-77f394d0ecb8。執行器設定的應用程式名稱為「bumble_ops_assistant」，但根層級代理程式是從「/home/admin_/bumble-ops-assistant/app」載入，這表示應用程式名稱為「app」。請確認執行器 app_name 與該目錄相符，或在建構執行器時明確傳遞 app_name。不相符的 ID 會導致執行器找不到工作階段。如要在工作階段遺失時自動建立工作階段，請建構執行器時將 auto_create_session 設為 True。
要求代理程式修正權限問題後，大腿就開始運作了。
13. 部署及發布至 Gemini Enterprise [公開測試版]
我想使用自然語言部署及發布至 GE
因此請保留手動或自然語言選項
我要求部署代理程式，系統也將代理程式部署至 Agent Engine。請參閱圖片瞭解相關步驟，並建立相關指令
圖片 - agent-cli-deploy-1.png 至 agent-cli-deploy-4.png
I aksed gemini cli to publish to ge app
我使用了 - Publish to Gemini Enterprise App bumble-workshop-lab-test-1_1778167389086
請參閱下方的圖片，瞭解如何完成這項操作，並據此建立相應的指示
agent-cli-publish-1.png 至 agent-cli-publish-7.png