-
Notifications
You must be signed in to change notification settings - Fork 902
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
Add the ability to create an MSI on non-tagged builds #3465
Labels
Comments
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
Changed the logic for skipping an MSI build to skip it by default, and no longer depend on a tagged build. This will allow developers to generate an MSI by adding `--shouldBuildMsi=true`.
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
When running the builds in CI, we should generate the MSI as well. This will allow us to get an MSI for any build to test with if needed.
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
As with the previous commit, this adds the configuration for GitHub Actions. Thus allowing us to ensure the MSI is able to be built in GitHub Actions as well. When running the builds in CI, we should generate the MSI as well. This will allow us to get an MSI for any build to test with if needed.
10 tasks
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
Changed the logic for skipping an MSI build to skip it by default, and no longer depend on a tagged build. This will allow developers to generate an MSI by adding `--shouldBuildMsi=true`.
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
When running the builds in CI, we should generate the MSI as well. This will allow us to get an MSI for any build to test with if needed.
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
As with the previous commit, this adds the configuration for GitHub Actions. Thus allowing us to ensure the MSI is able to be built in GitHub Actions as well. When running the builds in CI, we should generate the MSI as well. This will allow us to get an MSI for any build to test with if needed.
corbob
added a commit
to corbob/choco
that referenced
this issue
Jun 13, 2024
As with the previous commit, this adds the configuration for GitHub Actions. Thus allowing us to ensure the MSI is able to be built in GitHub Actions as well. When running the builds in CI, we should generate the MSI as well. This will allow us to get an MSI for any build to test with if needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Checklist
Is Your Feature Request Related To A Problem? Please describe.
No response
Describe The Solution. Why is it needed?
When working on the MSI, currently you need to tag your commit so that the Chocolatey.Cake.Recipe will generate the MSI. It would be beneficial to have the MSI be able to be built without a git tag.
Additional Context
No response
Related Issues
No response
The text was updated successfully, but these errors were encountered: