Comments
2 comments
-
Hi,
Thanks for your suggestion. I've added your suggestion to our UserVoice site. That's usually the best place to post feature requests as in addition to making suggestions you can vote on suggestions that other people have made. -
Looks like these two other items on UserVoice are kind of in the same space. One looks like it is directly related to using SemVar and the other would just let you run the build or tests but package up your code on your own.
We are currently in the same boat trying to figure out how to leverage SemVar with our DB Packages. One suggestion on the first item below was to run SQL CI with powershell. That might be a good work around for you until one of the UserVoice items get's enough votes to be implemented or maybe the acquisition of ReadyRoll and their support for SemVar trickles into the DLM tools
https://redgate.uservoice.com/forums/267000-dlm-automation/suggestions/11064639-as-an-build-engineer-i-d-like-to-be-able-to-overri
https://redgate.uservoice.com/forums/267000-dlm-automation/suggestions/9107827-ability-to-run-build-and-package-steps-separately
Add comment
Please sign in to leave a comment.
I tried to create NuGet package in TeamCity using "Redgate DLM Automation Build" step with package version set to: which is SemVer 2.0.0 compliant version number. Unfortunately I got this error message: It's because of the dot in prerelease tag.
Next step in my process is uploading package to Octopus Deploy's internal NuGet feed (which already supports SemVer 2.0.0) and updating databases using DLM Automation templates.
Thing to note is that NuGet 3.5.0 (currently in rc state) is going to support SemVer 2.0.0. It's explained on one of the NuGet's devs blog:
http://emgarten.com/2016/08/09/semver-2-0-0-with-nuget-3-5-0-rc1/
Any chance that DLM Automation could support SemVer 2.0.0?