Skip to content
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

Extend Download Pulumi Cron to check for package version on WinGet #10667

Closed
mikhailshilkov opened this issue Sep 9, 2022 · 0 comments · Fixed by #10949
Closed

Extend Download Pulumi Cron to check for package version on WinGet #10667

mikhailshilkov opened this issue Sep 9, 2022 · 0 comments · Fixed by #10949
Assignees
Labels
area/build CI/CD for pulumi/pulumi kind/engineering Work that is not visible to an external user os/windows resolution/fixed This issue was fixed
Milestone

Comments

@mikhailshilkov
Copy link
Member

We have no active monitoring of whether WinGet publishing succeeded and usually wait for community members to ask questions before we detect a problem. I suggest extending the Download Pulumi Cron action with a step to check WinGet.

@mikhailshilkov mikhailshilkov added os/windows area/build CI/CD for pulumi/pulumi kind/engineering Work that is not visible to an external user labels Sep 9, 2022
@mikhailshilkov mikhailshilkov changed the title Extend Download Pulumi Cron to check for package version on NuGet Extend Download Pulumi Cron to check for package version on WinGet Sep 9, 2022
@bors bors bot closed this as completed in 92c5a37 Oct 7, 2022
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Oct 7, 2022
iwahbe pushed a commit that referenced this issue Oct 10, 2022
10949: Add winget and msi install checks in download cron job r=Zaid-Ajaj a=Zaid-Ajaj

<!---
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

Fixes #10667

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [ ] I have added tests that prove my fix is effective or that my feature works
<!---
User-facing changes require a CHANGELOG entry.
-->
- [ ] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->

10954: Fix cloning from ADO repos r=Frassle a=Frassle

<!---
Thanks so much for your contribution! If this is your first time contributing, please ensure that you have read the [CONTRIBUTING](https://github.com/pulumi/pulumi/blob/master/CONTRIBUTING.md) documentation.
-->

# Description

<!--- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. -->

Small path bug, "git clone" by default clones to a new folder based on the last part of the repo name. So running something like `pulumi new https://fraser0275@dev.azure.com/fraser0275/fraser/_git/fraser` resulted in us making a folder like /tmp/pulumi-templates-1234/fraser with all the templates in it. That last part of the path was unexpected, because when we use gogit it clones directly into the target directory we give it.

Simple fix to just add `.` to the git clone command. I also added some logging while I was about here, given it helped me work out this issue.

Fixes #10886

## Checklist

<!--- Please provide details if the checkbox below is to be left unchecked. -->
- [x] I have added tests that prove my fix is effective or that my feature works. **No but I did manually check I could download templates from azure devops.**
<!---
User-facing changes require a CHANGELOG entry.
-->
- [x] I have run `make changelog` and committed the `changelog/pending/<file>` documenting my change
<!--
If the change(s) in this PR is a modification of an existing call to the Pulumi Service,
then the service should honor older versions of the CLI where this change would not exist.
You must then bump the API version in /pkg/backend/httpstate/client/api.go, as well as add
it to the service.
-->
- [ ] Yes, there are changes in this PR that warrants bumping the Pulumi Service API version
  <!-- `@Pulumi` employees: If yes, you must submit corresponding changes in the service repo. -->

Co-authored-by: Zaid Ajaj <zaid.naom@gmail.com>
Co-authored-by: Fraser Waters <fraser@pulumi.com>
@mikhailshilkov mikhailshilkov added this to the 0.79 milestone Oct 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/build CI/CD for pulumi/pulumi kind/engineering Work that is not visible to an external user os/windows resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants