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

Establish CI/CD using Azure Pipelines (Build/Release) #3621

New Issue
Closed
opened 2026-01-30 23:25:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:25:39 +00:00
Owner
Copy Link

Originally created by @WSLUser on GitHub (Aug 28, 2019).

Description of the new feature/enhancement

Create a Release Pipeline that pushes the release to the Github Release page. There is already a Build Pipeline so half of the battle is already done. Just need to copy it and adjust to go to master as the current one is for PR checking. Then once a week, the Release Pipeline would deploy to the Github Release page. An eventual todo is setup a deploy to the Microsoft Store in addition to the Github Release page.

A clear and concise description of what the problem is that the new feature would solve.

Automates the deployment of the app in addition to starting the set up of an update schedule.

A clear and concise description of what you want to happen.

I'd like to see releases more frequently from Github that require little administrative effort from the core team.

Originally created by @WSLUser on GitHub (Aug 28, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Create a Release Pipeline that pushes the release to the Github Release page. There is already a Build Pipeline so half of the battle is already done. Just need to copy it and adjust to go to master as the current one is for PR checking. Then once a week, the Release Pipeline would deploy to the Github Release page. An eventual todo is setup a deploy to the Microsoft Store in addition to the Github Release page. **A clear and concise description of what the problem is that the new feature would solve.** Automates the deployment of the app in addition to starting the set up of an update schedule. **A clear and concise description of what you want to happen.** I'd like to see releases more frequently from Github that require little administrative effort from the core team.
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-30 23:25:40 +00:00
claunia commented 2026-01-30 23:25:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 3, 2019):

We've actually got one, we're just not publishing the builds from it.

@DHowett-MSFT commented on GitHub (Sep 3, 2019): We've [actually got one](https://github.com/microsoft/terminal/blob/master/build/pipelines/release.yml), we're just not publishing the builds from it.
claunia commented 2026-01-30 23:25:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 3, 2019):

(We're not quite ready for that, because we need to settle on our cadence; that's more of a project management issue than a bug/feature here.)

@DHowett-MSFT commented on GitHub (Sep 3, 2019): (We're not quite ready for that, because we need to settle on our cadence; that's more of a project management issue than a bug/feature here.)
claunia commented 2026-01-30 23:25:41 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Sep 3, 2019):

Yeah, as I said, I was hoping to see more releases get published for testing instead of having to build to get more frequent from master. I would be fine doing this myself but unfortunately I lack the necessary permissions in Azure. I specified a week as a starting point for the Release due to that cadence not being quite settled yet (and the deployment can be cancelled if need be). It'll be easy enough to adjust the deployment schedule once everything settles down.

@WSLUser commented on GitHub (Sep 3, 2019): Yeah, as I said, I was hoping to see more releases get published for testing instead of having to build to get more frequent from master. I would be fine doing this myself but unfortunately I lack the necessary permissions in Azure. I specified a week as a starting point for the Release due to that cadence not being quite settled yet (and the deployment can be cancelled if need be). It'll be easy enough to adjust the deployment schedule once everything settles down.
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 Issue-Feature 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#3621
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?