[release/v7.5.6] Create Linux LTS deb/rpm packages for LTS releases#27163
Conversation
adityapatwardhan
added
the
CL-BuildPackaging
There was a problem hiding this comment.
Pull request overview
Backports Linux packaging template changes to generate LTS-flavored packages when a release is marked as LTS (and not a rebuild branch), enabling creation of LTS deb/rpm artifacts on the release/v7.5.6 branch.
Changes:
- Adds an additional
Start-PSPackageinvocation with-LTSwhen$metadata.LTSRelease.Packageis true. - Moves the “LTS Release” verbose logging closer to the packaging execution.
There was a problem hiding this comment.
The new LTS block will run for any packageType that uses this template. In this repo, linux-package-build.yml is invoked for many non-deb/rpm types (tar, fxdependent, min-size, etc.) via .pipelines/PowerShell-Packages-Official.yml, so LTS builds will now produce additional LTS variants for all those types as well. If the intent is only to add LTS deb/rpm support (per PR title/description), gate this block to deb/rpm package types (or split the template) so tar/fxdependent jobs don’t unexpectedly double their outputs/work.
Backport of #27049 to release/v7.5.6
Triggered by @adityapatwardhan on behalf of @daxian-dbw
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Required tooling change: Adds Linux LTS package (deb/rpm) support to the release branch's build infrastructure. This ensures v7.5.x LTS releases can be distributed as proper deb/rpm packages, which is critical for enterprise deployments on Linux systems.
Customer Impact
Linux LTS releases require properly packaged deb/rpm distributions for user installation.
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Backport verified by successful cherry-pick with no conflicts. Package generation for LTS releases was validated on v7.6 release branch. Verification includes: 1) CI pipeline confirmation on release branch, 2) Review of packaging configuration changes applied correctly, 3) Validation that LTS release tags trigger proper deb/rpm package builds.
Risk
REQUIRED: Check exactly one box.
Medium risk: This adds Linux LTS deb/rpm package support that was already validated in v7.6. The change is scoped to packaging configuration with minimal impact to core functionality. Verified by successful CI on v7.6 releases.