This PR is part ofcoder/coder#18827 which introduces new build reason values to identify what type of connection triggered a workspace build, helping to troubleshoot workspace-related issues.

kacpersaw added2 commits

July 14, 2025 14:46

Set 'jetbrains_connection' as build reason on workspace start

727fd4f

Fix tests

8088af5

Copy link

Contributor

github-actionsbot commentedJul 14, 2025

Qodana Community for JVM

23 new problems were found

Inspection name	Severity	Problems
`Usage of API marked for removal`	🔴 Failure	13
`Local 'var' is never modified and can be declared as 'val'`	🔶 Warning	1
`Incorrect string capitalization`	🔶 Warning	1
`Constant conditions`	🔶 Warning	1
`Usage of redundant or deprecated syntax or deprecated symbols`	🔶 Warning	1
`Redundant nullable return type`	🔶 Warning	1
`String concatenation that can be converted to string template`	◽️ Notice	2
`Argument could be converted to 'Set' to improve performance`	◽️ Notice	1
`Class member can have 'private' visibility`	◽️ Notice	1
`Redundant lambda arrow`	◽️ Notice	1

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

Register atQodana Cloud andconfigure the action
UseGitHub Code Scanning with Qodana
HostQodana report at GitHub Pages
Inspect and useqodana.sarif.json (seethe Qodana SARIF format for details)

To get*.log files or any other Qodana artifacts, run the action withupload-result option set totrue,
so that the action will upload the files as the job artifacts:

      -name:'Qodana Scan'uses:JetBrains/qodana-action@v2023.3.2with:upload-result:true

Contact Qodana team

Or via our issue tracker:https://jb.gg/qodana-issue
Or share your feedback:https://jb.gg/qodana-discussions

kacpersaw mentioned this pull request

Jul 14, 2025

feat: extend workspace build reasons to track connection typescoder/coder#18827

Merged

kacpersaw marked this pull request as ready for review

July 14, 2025 15:32

kacpersaw requested a review fromfioan89

July 15, 2025 14:16

fioan89 approved these changes

Jul 21, 2025

View reviewed changes

Copy link

Collaborator

fioan89 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

LGTM

kacpersaw added a commit to coder/coder that referenced this pull request

Jul 22, 2025

feat: extend workspace build reasons to track connection types (#18827)

482463c

This PR introduces new build reason values to identify what type ofconnection triggered a workspace build, helping to troubleshootworkspace-related issues.## Database MigrationAdded migration 000349_extend_workspace_build_reason.up.sql that extendsthe build_reason enum with new values:```dashboard, cli, ssh_connection, vscode_connection, jetbrains_connection```## ImplementationThe build reason is specified through the API when creating newworkspace builds:- Dashboard: Automatically sets reason to `dashboard` when users startworkspaces via the web interface- CLI `start` command: Sets reason to `cli` when workspaces are startedvia the command line- CLI `ssh` command: Sets reason to ssh_connection when workspaces arestarted due to SSH connections- VS Code connections: Will be set to `vscode_connection` by the VS Codeextension through CLI hidden flag(coder/vscode-coder#550)- JetBrains connections: Will be set to `jetbrains_connection` by theJetbrains Toolbox(coder/coder-jetbrains-toolbox#150) andJetbrains Gateway extension(coder/jetbrains-coder#561)## UI Changes:* Tooltip with reason in Build history<img width="309" height="457" alt="image"src="https://github.com/user-attachments/assets/bde8440b-bf3b-49a1-a244-ed7e8eb9763c"/>* Reason in Audit Logs Row tooltip<img width="906" height="237" alt="image"src="https://github.com/user-attachments/assets/ebbb62c7-cf07-4398-afbf-323c83fb6426"/><img width="909" height="188" alt="image"src="https://github.com/user-attachments/assets/1ddbab07-44bf-4dee-8867-b4e2cd56ae96"/>