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

Move the chocolatey config directly into this repo #9023

Open
tas50 opened this issue Oct 25, 2019 · 2 comments

Comments

@tas50
Copy link
Member

@tas50 tas50 commented Oct 25, 2019

Describe the Enhancement:

Move the chocolatey config to this repo and handle promotions of those packages just like any other package.

Describe the Need:

We want to make sure as soon as we promote Chef Infra Client that we publish the new version to chocolatey.org without a person having to do it by hand. It's basically the only by hand action in the Chef release at this point other than the overall announcement and only a few people even have permission to do it.

@robbkidd

This comment has been minimized.

Copy link
Member

@robbkidd robbkidd commented Oct 25, 2019

Another option for automated choco publishing could be to wire up https://github.com/chef/chocolatey-packages with expeditor subscriptions to omnibus packages getting promoted to stable to trigger expeditor performing a scripted update to the files there and having that repo do the publish. I haven't thought deeply yet about the trade-offs between these two options, though.

@robbkidd

This comment has been minimized.

Copy link
Member

@robbkidd robbkidd commented Oct 25, 2019

🤔 🤔 🤔 🤔

Though, as you said, there's something to be said for chef/chef owning the destiny of all its artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.