Skip to content

Conversation

@TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Feb 26, 2020

PR Summary

Publish PowerShell vPack for stable and better builds

PR Context

This is related to windows engineering

PR Checklist

@ghost ghost assigned iSazonov Feb 26, 2020
# Conflicts:
#	tools/releaseBuild/setReleaseTag.ps1
@TravisEz13 TravisEz13 marked this pull request as ready for review February 26, 2020 21:18
@TravisEz13
Copy link
Member Author

Code is ready for review now.

value: 1
- name: POWERSHELL_TELEMETRY_OPTOUT
value: 1
- group: Azure Blob variable group
Copy link
Member Author

Choose a reason for hiding this comment

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

@adityapatwardhan Note that this YAML tells what variable groups it needs

displayName: 'Validate Zip and MSI Package Names'

- pwsh: |
$message = @()
Copy link
Member

Choose a reason for hiding this comment

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

seems $message is not used

displayName: Set Build Name for Non-PR
condition: ne(variables['Build.Reason'], 'PullRequest')

- template: ./templates/vpackReleaseJob.yml
Copy link
Member

Choose a reason for hiding this comment

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

Should we consider:

  1. Adding approvals?
  2. Execute only on build.reason manual?

Copy link
Member Author

@TravisEz13 TravisEz13 Feb 26, 2020

Choose a reason for hiding this comment

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

I did number 2

Let's leave 1 for when we integrate this into a deployment yaml.

@TravisEz13 TravisEz13 changed the title Publish PowerShell vPack for stable and better builds Publish PowerShell vPack for stable and better builds Feb 27, 2020
@TravisEz13 TravisEz13 merged commit c97f2d7 into PowerShell:master Feb 27, 2020
@TravisEz13 TravisEz13 deleted the publish_vpack branch February 27, 2020 18:13
@TravisEz13 TravisEz13 added this to the GA-approved milestone Feb 27, 2020
@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Feb 27, 2020
@TravisEz13 TravisEz13 modified the milestones: GA-approved, 7.0.0 Feb 27, 2020
@ghost
Copy link

ghost commented Mar 4, 2020

🎉v7.0.0 has been released which incorporates this pull request.:tada:

Handy links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants