Refactor Unified Release Build
- Make injecting the nuget.config a template
- Make setting the version variable a template
- Add parameters to templates where needed
- Run defender scan before uploading linux packages (and rename step to plain english)
Add compliance to Coordinated build
- Also switch to mac internal pool for release build
- Also turn some duplicate tasks into templates
- Also fix issue with vscode configuration which causes yaml files not to be recogized as yaml
Update the universal build to also build the framework package needed for the dotnet sdk container image.
## PR Context
We build the package in individual builds. This change brings over the steps in the universal build.
# Conflicts:
# tools/packaging/packaging.psm1
Create unified release build for macOS and Linux packages
- Also, updated the definition with latest definitions from the definitions in use.
I will work on these in future PRs:
- Add compliance Job
- Add macOS Signing step
- Merging Windows into the YAML
# Conflicts:
# tools/releaseBuild/azureDevOps/templates/linux.yml
Add function to create a new nuget.config file (#8170)
Add a function to create a NuGet.config file to consume packages from the specified feed URL using the specified credentials.
- Also, exclude the `nuget.config` file under `src/Modules` from being clean by `Start-PSBuild -clean`
# Conflicts:
# build.psm1
Change API to match cmdlet which is more reliable in AzDevOpsPipelines Windows (#8003)
# Conflicts:
# test/powershell/Modules/Microsoft.PowerShell.Management/Test-Connection.Tests.ps1
This PR combines all Windows PowerShell code changes needed for 6.1.
* Disallow ps1 files from being imported as modules in CL mode
* JEA loop back change to prevent code running in local session instead of remote session
* Debugger does not run commands with Internal origin when in CL mode
* Add support for new AMSI codes
* Unhandled exception fix
* Change to use AMSI buffer API
* Module vulnerabilities under CL mode
* Untrusted input tracking work
* Configuration keyword
* PSRP protocol version check for reconstruct reconnect
* Sharing initial session state over multiple runspace pool runspaces
* Restricted remote session in UMCI
* Applocker detection collision
* Help command exposing functions
Cherry picked from !5232
The variable was set to empty (meaning to delete the variable) in the non-preview case and the build fails.
The fix avoids setting the variable to empty
Add the functionality to build a framework dependent (shared framework) package for PowerShell.
The changes create two packages, one for Windows and other for Linux, due to #if code.
Add daily build non-windows platforms
- Also, make the [Feature] tag work in VSTS for non-windows
- Also, add a way to force feature tests to run
- Also, fix an issue where `-workingdirectory` didn't work when running async
Fixes underlying problem of #3341. Related: #2881
When multiple versions (e.g. RTM and preview) of PowerShell are installed via the MSI and one is being uninstalled, then the start menu shortcut does not get removed due to the shortcut component being not unique per version. This also applies to an upgrade scenario. Therefore use an auto-generated Guid (`*`)
Dongbo Wang