NOTE: RoundhousE is "abandoned"

RoundhousE is a wonderful tool, and I was one of the main maintainers for a couple of years, as no one else was maintaining it, and it provided great value to me. However, the project has been around for many years, and had begun accruing some technical debt that became tough to work with when trying to introduct new features or refactor.

After giving it some thought, I decided to start from zero, and create a successor to RoundhousE, starting from the ground up on modern .NET (started on .NET 6 in 2021, now on .NET 8), cross-platform, using the latest 3rd party libraries to connect to the various databases, etc. I removed NHibernate as a dependency, as it was only used to create the versioning tables, and seemed like a bit of an overkill, and it was hard to move fast forward technology wise with such a large dependency. Log4net was also replaced with Serilog.

RoundhousE will of course never disappear, and the source code will stay here. But, there is no active development of RoundhousE for now. I continue my journey with the successor, grate. It's now on version 1.6, and considered stable. It's in active development.

Please head over there, and try it out. If should be almost feature-complete with RoundhousE, and should you find anything that's missing, please file an issue, or submit a PR.

Project RoundhousE - Database Change Management done right

<a href=https://ci.appveyor.com/project/chucknorris/roundhouse> <img src="https://ci.appveyor.com/api/projects/status/github/chucknorris/roundhouse?branch=master&svg=true" alt="CI build status"/> </a>

<p></p> <img src="https://github.com/ferventcoder/roundhouse/raw/master/docs/logo/RoundhousE_Logo.jpg" height="200" alt="RoundhousE - Professional Database Management" />

LICENSE

Apache 2.0 - see docs\legal (just LEGAL in the zip folder)

Documentation

WIKI

INFO

Overview

RoundhousE is an automated database deployment (change management) system that allows you to use your current idioms and gain much more. Currently works with Oracle¹, SQL Server (2000/2005/2008/Express), Access¹, MySQL, SQLite and PostgreSQL. There are future plans for other databases.

It seeks to solve both maintenance concerns and ease of deployment. We follow some of the same idioms as other database management systems (SQL scripts), but we are different in that we think about future maintenance concerns. We want to always apply certain scripts (anything stateless like functions, views, stored procedures, and permissions), so we don't have to throw everything into our change scripts. This seeks to solves future source control concerns. How sweet is it when you can version the database according to your current source control version?

<a name="footnote1">1</a>) Only on full-framework on Windows, not on Cross-platform .NET Core global tool version.

Getting started with RoundhousE

Downloads

You can download RoundhousE from https://github.com/chucknorris/roundhouse/releases

You can also obtain a copy from the build server at https://ci.appveyor.com/project/chucknorris/roundhouse/build/artifacts.

Gems (Not updated for 0.9.0 and above, sorry)

If you have Ruby 1.8.6+ (and Gems 1.3.7+) installed, you can get the current release of RoundhousE to your machine quickly!

1. Type gem install roundhouse
2. Then from anywhere you can type rh [options]

NuGet

With NuGet you can get the current release of RoundhousE to your application quickly!

1. In Visual Studio Package Manager Console type install-package roundhouse
2. There is also roundhouse.lib, roundhouse.msbuild, and roundhouse.refreshdatabase

Chocolatey

Chocolatey is like apt-get, but for Windows! This is an alternative method to get the current release of RoundhousE to your machine quickly!

1. Type cinst roundhouse
2. Then from anywhere you can type rh [options]

Dotnet core global tool (Windows, Linux, macOS, etc)

1. Type dotnet tool install -g dotnet-roundhouse
2. Then from anywhere you can type rh [options]

You can read more about what happens in the background e.g. here: https://natemcmaster.com/blog/2018/05/12/dotnet-global-tools/, but in short, it installs the binaries to your ~/.dotnet/tools folder.

You will need dotnet core installed on your box for this to work. You can get it here: https://dot.net.

Docker: Dotnet core global tool

You can easily integrate RoundhousE in your existing docker infrastructure. Use docker compose, or just pull it down directly and run it. You should probably build upon the image, and add your own customisations, as appropriate. The docker image has the dotnet core global tool distribution of RoundhousE in a Debian 10 Linux base image.

1. Type docker pull dotnetroundhouse/roundhouse
2. Type docker run dotnetroundhouse/roundhouse

Source

This is the best way to get to the bleeding edge of what we are doing.

1. Clone the source down to your machine.
   git clone git://github.com/chucknorris/roundhouse.git
2. Type cd roundhouse
3. Type git config core.autocrlf false to leave line endings as they are.
4. Type git status. You should not see any files to change.
5. Run build.ps1. NOTE: You must have git on the path (open a regular command line and type git).

Developing

The build system has been using UppercuT, but this will probably not be maintained going forward. We will try to standardize on more "main stream" build tools like MSBuild and Powershell. There are still some remains of UppercuT in the source code (esp. in the build folder), but this is probably going to be removed in the near future.

To work with the command line, you will need the following in your path:

• MS Build
• GitVersion (easiest to run choco install gitversion.portable. You are running chocolatey aren't you?)
• NuGet Command Line (easiest to run choco install nuget.commandline. You are running chocolatey aren't you?)

IMPORTANT

NOTE: If you are looking at the source - please run build.ps1 before opening the solution. It extracts the keywords.txt files needed for ILMerge-ing MySql dlls, and build will complain without them.

REQUIREMENTS

• .NET Framework 4.6.1 (for the full framework version), or
• .NET Core 2.1+ (for the dotnet core distribution)
• SA access to the sql server (for creation or deletion)
• change access to the database (for everything else)

DONATE

Donations Accepted - If you enjoy using this product or it has saved you time and money in some way, please consider making a donation.
It helps keep to the product updated, pays for site hosting, etc. https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=2RA38UKSK6EZU

RELEASE NOTES

Please see releases for the full release logs

1.0.2

Bugfix release

Fixed bug in packaging of dotnet core tool, and another bug with log folder paths and colon in connection string.

1.0.1

Merge-error release fix

1.0.0

Cross-platform dotnet core and dotnet standard ++

Big technological release. RoundhousE now runs on .NET Core in addition to the good, old .NET framework.

0.9.1

Two Bugfixes

After the 0.9.0 release, users identifed two significant bugs. These are fixed in a quick point release.

(See release for the full release notes)

0.9.0

Focus on modernising tooling

RoundhousE has had some catching-up to do tooling-wise. Dependency on .NET 3.5, old, NAnt-based build chain, etc. We are starting this work. It is not done yet, but on its way. Feature-wise not a lot to brag about, but RH.exe should now be able to run on Windows Server 2016 out-of-the-box, because it is no longer dependent on .NET 3.5.

(See release for the full release notes)

0.8.8

Catching up with Pull Requests (See release for the release notes)

0.8.7

OMG!! It's a RoundhousE release!!

It's been a long time coming. I didn't want to get bogged down into writing the perfect release notes, so I am summarizing the last four years of commit history. I hope that no one that contributed feels slighted by my failure to specifically acknowledge your contribution. I intend to do better in the future.

Enhancements

• Added option to run scripts outside of transaction scope
• Handle Azure connection strings
• Properly split files that start with a splitter
• Respect Transaction flag
• Improved Logging
• Added switch --warnandignoreononetimescriptchanges

Bug Fixes

• Only retry on SQL Connection errors
• Correctly handle postgres connection disposed error

0.8.6

Enhancements

• Use git as official repository. (mpareja)
• Upgrade UpperCut to version 1.4.2. (ferventcoder)
• Database Restore: use restore specific timeout value. (icetoast - pull #90)
• Ignore EOL format changes when detecting script changes. (lahma - pull #104)
• Include