-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic: Implement remaining JetBrains IDE's (CLion, WebStorm, Rider, RubyMine) #7751
Comments
I think it depends on #7023 Till we cannot do it automatically with smoke testing it will be tedious to review so many PRs. |
Is there any expected time of arrival for other IDEs support? |
Hey @sinansonmez, thanks for stopping by!
Gitpod current focus is on the IntelliJ experience (which has a lot of overlap with the other JetBrains IDEs), which is also where JetBrains themselves are focussing a lot of their remote development energy. As the experience improves for the other IDEs we'll be looking to roll those as soon as we reasonably can 🙏 |
Waiting for the CLion support :) |
With gitpod-io/leeway#93 done, we can simplify our build process to add more components easier. |
Can't wait for Rider |
Hey folks, wanted to give a quick update (as many have asked!). Firstly, thanks so much to all our users who have given feedback in the community for our JetBrains integration. Please continue to do so, we're learning a lot from you and we're able to refine the experience based on your input. Special shoutout to Gitpod community hero @buggtb for your constant feedback and positive energy. If you're late to the party, I wanted to give a little background and context into Gitpod IDE support and why we've not yet released full support of the IDEs just yet. For background, we have a partnership with JetBrains. In real terms is that we have conversations with the friendly JetBrains people to help input on the future of JetBrains Gateway as a whole and help create a really great remote dev experience with JetBrains in Gitpod and beyond! Opening up an IDE is only one step in the process to bringing a great developer experience in Gitpod. Whilst a lot of the Gitpod functionality is shared across the JetBrains IDEs, such as prebuild support, integration of Gitpod task terminals, port forwarding and port behaviours. There are also lots of language specific product changes that need to be made in both Gitpod and JetBrains. For example:
For that reason we've been a bit deliberate in how (and when) we roll out other IDE support. We don't want to open up an IDE for our Gitpod users to go try the integration, but then be dissapointed (let's say if some aspect of the integration is not up to the standard they expect, some plugin doesn't work, etc). In simpler terms: The quality of the experience is really important to us. We actually just opened up WebStorm and RubyMine (yet to be announced). So we're optimistic that we can get to the remaining IDEs opened in beta in the coming weeks ! Come join us on Discord, chat about your experience and give us your feedback (we are listening!). We're super excited for what's to come with JetBrains + Gitpod 🙏 |
Shipped! 🚢 🚀
|
Rider + CLion added to Gitpod, needs announcing in changelog and then we can close this issue 🙏 |
Closing as complete ✅ |
We are currently only supporting the following JetBrains IDE's
However, we need to add remote development backends support for:
Related:
Front conversations
Callout: 👋 Are you interested in this feature? We would be interested to talk to you to hear your feedback.
Internal conversation [1]
The text was updated successfully, but these errors were encountered: