starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

[Question]: Is there a way to try out build artifacts? #14329

New Issue
Closed
opened 2026-01-31 04:07:20 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 04:07:20 +00:00
Owner
Copy Link

Originally created by @rashil2000 on GitHub (Jun 24, 2021).

Each commit fires off a build (for testing/CI). Let's say I want to manually test out a particular commit, for example 265bdc777a

I clicked on the little green checkmark and went to Azure pipelines page, and downloaded the Release artifact (for x64) - named drop.zip. (link here)

I tried both appx and Release folders (wt.exe and WindowsTerminalUniversal.exe), tried merging the relevant folders (for x64) and all, but everytime I clicked on wt.exe, the cursor spun for a second and then nothing happens.

So my question is, is there no way to test any commits out without actually building the VS solution?

Originally created by @rashil2000 on GitHub (Jun 24, 2021). Each commit fires off a build (for testing/CI). Let's say I want to manually test out a particular commit, for example 265bdc777a7e6d141e9a90507817aa8f9e0c7ea3 I clicked on the little green checkmark and went to Azure pipelines page, and downloaded the Release artifact (for x64) - named `drop.zip`. (link [here](https://dev.azure.com/ms/terminal/_build/results?buildId=184228&view=artifacts&pathAsName=false&type=publishedArtifacts)) I tried both appx and Release folders (wt.exe and WindowsTerminalUniversal.exe), tried merging the relevant folders (for x64) and all, but everytime I clicked on wt.exe, the cursor spun for a second and then nothing happens. So my question is, is there no way to test any commits out without actually building the VS solution?
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 04:07:20 +00:00
claunia commented 2026-01-31 04:07:21 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jun 24, 2021):

There used to be artifacts that you could use to test but when they updated the build pipeline early on last year, the artifacts ceased to be generated as often in order to increase the speed of the build (as slow as it is, it used to be much slower as a result of generating an artifact with almost every PR). So if there's a specific commit you want to test, you'll need to build it. VSCode should be able to be used instead by default in this project if you have the necessary configuration set up.

@WSLUser commented on GitHub (Jun 24, 2021): There used to be artifacts that you could use to test but when they updated the build pipeline early on last year, the artifacts ceased to be generated as often in order to increase the speed of the build (as slow as it is, it used to be much slower as a result of generating an artifact with almost every PR). So if there's a specific commit you want to test, you'll need to build it. VSCode should be able to be used instead by default in this project if you have the necessary configuration set up.
claunia commented 2026-01-31 04:07:21 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Jun 24, 2021):

But the artifacts that I downloaded already has the wt executable and the related DLLs. Is it not a complete build?

I have VSCode set up with Visual Studio Build Tools (they were required by the Rust MSVC toolchain), but I guess that won't be enough, since I don't have the Desktop Development with C++ workload installed in VS?

@rashil2000 commented on GitHub (Jun 24, 2021): But the artifacts that I downloaded already has the wt executable and the related DLLs. Is it not a complete build? I have VSCode set up with Visual Studio Build Tools (they were required by the Rust MSVC toolchain), but I guess that won't be enough, since I don't have the Desktop Development with C++ workload installed in VS?
claunia commented 2026-01-31 04:07:21 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Jun 24, 2021):

Yeah, it's way easier to build in VS as it'll tell you what to install. There are still some random artifacts created (or not, depends if a test build is needed by the MS devs) but you won't find one for every commit. In order to use an artifact, you'd have to go the unsupported route of running wt.exe directly rather than installing the msix. Also, this project doesn't use Rust so that's not even a factor. I don't think there any plans for a long time to switch to Rust. Alot of deps used are C++ specific though a few are fed in from Nuget.

@WSLUser commented on GitHub (Jun 24, 2021): Yeah, it's way easier to build in VS as it'll tell you what to install. There are still some random artifacts created (or not, depends if a test build is needed by the MS devs) but you won't find one for every commit. In order to use an artifact, you'd have to go the unsupported route of running wt.exe directly rather than installing the msix. Also, this project doesn't use Rust so that's not even a factor. I don't think there any plans for a long time to switch to Rust. Alot of deps used are C++ specific though a few are fed in from Nuget.
claunia commented 2026-01-31 04:07:21 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Jun 24, 2021):

In order to use an artifact, you'd have to go the unsupported route of running wt.exe directly rather than installing the msix.

Yes, that's what I did.

Also, this project doesn't use Rust so that's not even a factor. I don't think there any plans for a long time to switch to Rust.

I was not saying that this project uses Rust. I was just mentioning why I had Visual Studio Build Tools installed.

@rashil2000 commented on GitHub (Jun 24, 2021): > In order to use an artifact, you'd have to go the unsupported route of running wt.exe directly rather than installing the msix. Yes, that's what I did. > Also, this project doesn't use Rust so that's not even a factor. I don't think there any plans for a long time to switch to Rust. I was not saying that this project uses Rust. I was just mentioning why I had Visual Studio Build Tools installed.
claunia commented 2026-01-31 04:07:22 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Jun 25, 2021):

I got it working. The artifact was complete, I was just looking at the wrong msix file.

According to the Readme:

I built and ran the new Terminal, but it looks just like the old console

Cause: You're launching the incorrect solution in Visual Studio.

Solution: Make sure you're building & deploying the CascadiaPackage project in
Visual Studio.

I extracted the CascadiaPackage_0.0.1.0_x64.msix and used that. Bold text looks awesome!

@rashil2000 commented on GitHub (Jun 25, 2021): I got it working. The artifact was complete, I was just looking at the wrong msix file. According to the Readme: > ### I built and ran the new Terminal, but it looks just like the old console > > Cause: You're launching the incorrect solution in Visual Studio. > > Solution: Make sure you're building & deploying the `CascadiaPackage` project in > Visual Studio. I extracted the `CascadiaPackage_0.0.1.0_x64.msix` and used that. Bold text looks awesome!
claunia commented 2026-01-31 04:07:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 25, 2021):

Glad you got it working! I'd like to provide nightlies and runnable CI artifacts, but we haven't done the leg work to make sure they're code signed and deployable anywhere easily. Alas!

@DHowett commented on GitHub (Jun 25, 2021): Glad you got it working! I'd like to provide nightlies and runnable CI artifacts, but we haven't done the leg work to make sure they're code signed and deployable anywhere easily. Alas!
claunia commented 2026-01-31 04:07:22 +00:00
Author
Owner
Copy Link

@rashil2000 commented on GitHub (Jun 25, 2021):

I imagine it'd be too much trouble to code sign the builds for every commit/PR, but thanks for the consideration!

@rashil2000 commented on GitHub (Jun 25, 2021): I imagine it'd be too much trouble to code sign the builds for every commit/PR, but thanks for the consideration!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Needs-Tag-Fix Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14329
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?