Our existing Rails application is being ported to run inside of Docker. On TeamCity, we see the following message coming out of the Command Line build step where we invoke `docker run [...] rake test`:
"RubyMine reporter works only if it test was launched using RubyMine IDE or TeamCity CI server"
This message appears in the build log immediately before the default reporter kicks in. While the tests do execute, the results are opaque to TeamCity - it doesn't understand how many tests ran, passed, etc. Looking at the source of MiniTest's RubyMineReporter, it seems like the LoadErrors that are causing this could be addressed if we were to expose the contents of plugins/rake-runner/rb to Docker, but it isn't clear that would be sufficient - it looks like sm_factory_provider_loader.rb might need to be sourced for example.
Is there an existing reference implementation that yields the benefits conveyed by the TeamCity RakeRunner (as we experience it from traditional Rake build steps) when the Ruby environment itself is within a Docker container? If not, what's required to get the RubyMineReporter to act like it normally would from a Rake build step?