Skip to content

Fix New-Release cmdlet by also building also for v4 and misc. improvements #996

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

bergmeister
Copy link
Collaborator

PR Summary

  • Important fix is to also build the release for v4.
  • I also reorded it so that it builds v 3,4,5,6 in order to satisfy my inner OCD. ;)
  • Minor improvement of error message for platyPS requirement check

PR Checklist

Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

  • PR has a meaningful title
    • Use the present tense and imperative mood when describing your changes
  • Summarized changes
  • User facing documentation needed
  • Change is not breaking
  • NA Make sure you've added a new test if existing tests do not effectively test the code changed
  • This PR is ready to merge and is not work in progress
    • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

@bergmeister bergmeister added this to the 1.17 milestone May 10, 2018
@bergmeister bergmeister self-assigned this May 10, 2018
@bergmeister bergmeister requested a review from JamesWTruher May 10, 2018 21:28
.\buildCoreClr.ps1 -Framework net451 -Configuration PSV3Release -Build
.\buildCoreClr.ps1 -Framework net451 -Configuration PSV4Release -Build
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The essential bug was that it was not being built for version 4, the rest is just re-ordering that it builds v 3,4,5,6 in order for better readability

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the 1.16.1 version of Script Analyzer did not include a PSv4 directory. So we haven't shipped it for a long while. Has there been an issue with this? Is there any strong reason why we should start shipping a v4 version when we haven't previously?

Copy link
Contributor

@JamesWTruher JamesWTruher left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we should release a v4 version

.\buildCoreClr.ps1 -Framework net451 -Configuration PSV3Release -Build
.\buildCoreClr.ps1 -Framework net451 -Configuration PSV4Release -Build
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the 1.16.1 version of Script Analyzer did not include a PSv4 directory. So we haven't shipped it for a long while. Has there been an issue with this? Is there any strong reason why we should start shipping a v4 version when we haven't previously?

@bergmeister
Copy link
Collaborator Author

bergmeister commented May 11, 2018

@JamesWTruher we already used to ship a folder for psv34 (and fullclr and coreclr) but PR #919 that fixed the references to SMA to be correct, split v3 and v4 (leading to much better behaviour for v3). The psm1 file has custom code here to pick the right binaries for the right version. PSSA will not work on v4 without this PR

@JamesWTruher JamesWTruher merged commit 606c9eb into PowerShell:development May 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants