Release on every build? #940
andrew-welker
started this conversation in
CI/CD
Replies: 1 comment 2 replies
-
Just my 2 cents; I still prefer to have everything as a package in NUGET |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
After trying to find a certain Essentials release, I'm rethinking creating a Github Release for every build we do using the CI/CD pipeline. Its becoming noise to some extent. I'm thinking beta builds should still create a release (builds from the development branch). For using certain Essentials builds in plugins, Nuget would be the preferred delivery mechanism. For downloading an .cpz to install on a processor, the build.zip artifact can be downloaded from a workflow run. Commits would still be tagged with the release number in this scenario. Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions