Today we have updated our Early Access Program for the upcoming 2017.1 release. If you haven’t tried it yet, you’re welcome to download the newest RubyMine 2017.1 EAP3 from our What’s new page.
In the previous EAP post we announced quick gemset creation and RuboCop support. This small yet important update complements the previously announced EAP with the ability to create classes nested in the right modules by using the New Ruby Class dialog:
RubyMine 2017.1 EAP 2 (171.2272.16) is out and available for download. Besides a number of bug fixes, this Early Access Program provides a way to create RVM gemsets for Rails applications right from the New Project wizard, and features Rubocop support.
Creating Gemsets From the New Project Wizard
If you haven’t used gemsets before, you might want to know that a gemset is a container used to keep separate gems for each project. Gemsets allow you to change gems and their versions in one project without being afraid of affecting your other projects. Jump to the RVM documentation to learn how gemsets can improve your coding experience.
To create a gemset for your new Rails project in RubyMine, follow these steps:
Open RubyMine and click Create New Project from the Welcome screen (File | New Project). Choose a new Rails application.
We’re glad to bring out RubyMine 2017.1 EAP (171.2014.20) containing both new features and significant bug fixes. In this post we’d like to highlight a new feature for Puppet: Puppet Project Structure.
Puppet Project Structure
In the recently released RubyMine 2016.3, we announced more intelligent Puppet support, which provides better code completion and navigation along with other fundamental capabilities. But in this update, we think we have finally made a decent tool for developing Puppet modules, which are the most popular approach to Puppet development:
RubyMine 2016.3.1 is now released and available for download from our website. If you are running the earlier stable release, RubyMine 2016.3, you will soon be notified about the available patch-update.
This update fixes several important bugs:
- Run with Coverage works correctly on all operating systems.
- Regained running RSpec tests within it..end blocks.
- Fixed search by namespaced class name.
- Fixed random freezes related to the Ruby UML Support Integration plugin.
Posted in Announcement
It’s been only a week since we announced RubyMine 2016.3, but we’re already back on track with RubyMine 2016.3.1 EAP.
This update brings important bug fixes, both long-awaited and those discovered in the newest 2016.3 release. Here are the highlights:
We’re in high spirits having this year’s final update released today, and we invite you to share our joy and welcome RubyMine 2016.3! Learn more and get the newest version from our What’s New page!
Having an itch for consistency, we’ve worked to improve a number of existing features. The new version provides recently announced improved support for Puppet, much faster remote gem downloading, and new gem management UI.
That said, we didn’t forget to add new things to RubyMine. You will find the opportunity to attach the debugger to locally running Ruby/Rails processes, as well as full support for MiniTest::Spec.
Traditionally, a number of platform improvements were also inherited and tailored from IntelliJ IDEA, namely better VCS log, JS improvements, and updated database tools.
Today we’re glad to bring out the RubyMine 2016.3 RC (build 163.7743.40).
For previous posts covering the major new features of the upcoming release, see: New Gem Management UI, Faster Remote Gem Downloading, Better Puppet Support.
Attach to local process
Starting with v2016.3, RubyMine allows you to attach to locally running Ruby/Rails processes with the IDE’s debugger. The new feature makes it possible to debug an ongoing Ruby/Rails process, whether you are running it from the IDE, terminal, or a custom pipeline.
Imagine having a working Ruby/Rails project with a custom setup. Everything works properly, but there’s some annoying routine affecting your app’s performance. You’d probably want to investigate and fix the issue in that process without having to spend time configuring the debugging environment for the whole project.
You could use Rails autoloader and the newly inserted ‘binding.pry’ to start debugging session in console. However, Attach To Process will go far beyond that, allowing you to exploit the whole feature set of the RubyMine debugger without any configuration.
Please welcome the next minor update: RubyMine 2016.2.4. To update, download the new version from our website or, if you’re running RubyMine 2016.2.3, install the patch by clicking Check for Updates.
This update fixes an annoying wrong error highlighting bug. You can find a full list of all addressed issues in the release notes.
Your RubyMine Team
We are staying on track with the Early Access Program – please welcome the next RubyMine 2016.3 EAP build 163.4396.20.
For previous posts covering the major new features of the upcoming release, see: Faster Remote Gem Downloading.
New Gem Management UI
Gemsets seem to be the convenient way to deal with different gem environments for your apps. RubyMine has supported RVM gemsets for a while, and it’s been almost a year since we announced support for rbenv gemsets as well. But we were faced with the fact that a lot of gemsets make our Ruby version and gem management UI too complicated and not intuitive enough. In addition, rbenv and RVM gemsets behave in a slightly different way, so the task of making an intuitive and unified UI for both of these Ruby version managers becomes even more challenging. So that is the new UI we’ve come up with: