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
Ideally, we should create a release branch and complete all release tasks using that branch, including generating all packages and update all docs, and then push the release tag and merge the release branch to master.
However, this cannot be done currently because our build depends on the release tag to generate GitCommitId for $PSVersionTable. and thus the release tag has to be pushed before starting the release tasks.
To break this dependency, we should update Start-PSBuild to accept a GitCommitId string and update the Jenkins build script so that the GitCommitId string can be passed to the build pipeline.
Ideally, we should create a release branch and complete all release tasks using that branch, including generating all packages and update all docs, and then push the release tag and merge the release branch to master.
However, this cannot be done currently because our build depends on the release tag to generate
GitCommitIdfor$PSVersionTable. and thus the release tag has to be pushed before starting the release tasks.To break this dependency, we should update
Start-PSBuildto accept a GitCommitId string and update the Jenkins build script so that the GitCommitId string can be passed to the build pipeline.Tasks
Start-PSBuildandStart-PSPackageto accept aReleaseTagargument, which will override the git commit id retrieved fromgit describe. Resolved via Make 'Start-PSBuild' and 'Start-PSPackage' accept a release tag argument #3921.-ReleaseTagflag. Resolved by @TravisEz13 via Add release tag support PSRelease#13