We have a number of tools in our .NET shop. It all starts with GitHub Pull Requests. From there, we have a TeamCity CI build that reports status back to the GitHub PR. A green check mark is necessary for merging.
Post merge, we run a Build, Package, and Create Release build config in TeamCity. This creates a NuGet package for Octopus Deploy. We then push to separate environments using Octopus, and it's amazing. Best .NET deploy tool ever.
For new features, we utilize LaunchDarkly feature flags to roll out in a very specific way. This ensures low outage windows.
In the future, we will be running Runscope and/or Ghost Inspector tests post-deploy to ensure the updates didn't break core app functionality.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We have a number of tools in our .NET shop. It all starts with GitHub Pull Requests. From there, we have a TeamCity CI build that reports status back to the GitHub PR. A green check mark is necessary for merging.
Post merge, we run a Build, Package, and Create Release build config in TeamCity. This creates a NuGet package for Octopus Deploy. We then push to separate environments using Octopus, and it's amazing. Best .NET deploy tool ever.
For new features, we utilize LaunchDarkly feature flags to roll out in a very specific way. This ensures low outage windows.
In the future, we will be running Runscope and/or Ghost Inspector tests post-deploy to ensure the updates didn't break core app functionality.