You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if ($PSCmdlet.ParameterSetName-notin'GenerateMatrixJson','GenerateTagsYaml','DupeCheck','GenerateManifestLists'-and$Channel.Count-gt1)
241
+
if ($PSCmdlet.ParameterSetName-notin'GenerateMatrixJson','UpdateBuildYaml','GenerateTagsYaml','DupeCheck','GenerateManifestLists'-and$Channel.Count-gt1)
231
242
{
232
243
throw"Multiple Channels are not supported in this parameter set"
# Note: channelGroup contains entry for a channels' regular and channel's test-deps images.
692
+
# But, we only want 1 <channel>ReleaseStage.yml file to be created per channel (ie 1 stableReleaseStage.yml) so only populate start of yaml file once per channel.
Add-Content-Path $YamlFilePath-Value "$($sixSpace)imageName: $imageName"# ie. imageName: alpine317\test-deps (since this differs from artifactSuffix for test-deps images only, we have a separate entry as the yaml param)
This `updateBuildYamls.ps1` script needs to be run before the build pipeline for PowerShell-Docker is kicked off. Running the script will produce a channel based yaml file, like <channel>ReleaseStage.yml for each channel. Then a PR must be created with these newly added/updated yaml files as the build will rely on them.
6
+
7
+
## Running the Script
8
+
9
+
To update the releaseStage.yml file for all the channels, run `./updateBuildYamls.ps1 -StableVersion <stableVersion> -PreviewVersion <previewVersion> -LtsVersion <ltsVersion>`.
10
+
11
+
If you want the channel versions from channels.json to be used, simply omit the -*Version parameters and run, `./updateBuildYamls.ps1`.
12
+
13
+
## Notes
14
+
15
+
The versions provided must match versioning syntax rules for stable and preview versions. Valid examples include 7.4.2 (stable) and v7.4.0-preview.5 (preview)
0 commit comments