The git host and PR management system is well built, and was by far the highlight of using it. (Things like ticket relations and sub tasks that aren’t just check lists become pretty important imo to not losing things, vs just having everything be a free floating ticket) It worked well for our little project but I wouldn’t be able to use it on a larger project. Basically just tickets with IDs, that you could assign a status. I have actually used Spaces on a small side project with some friends up until a few months ago! It does seem to have improved since then, but when I was using it the project management/jira-ish features were pretty weak. If you are curious to learn about about Coherence, please check out our free beta at the link above or feel free to reach out to We appreciate any and all feedback from the HN community. We hope to integrate with them where it makes sense! Of course, we’re huge fans of JetBrains products, and them and the other companies mentioned above have so much credibility and such vast resources that they are going to deliver widely-used and powerful products. We do agree with the Space product thesis in that the Cloud IDE is a central piece of the next generation platform - we just think that tying it deeply to the deployment and cloud infrastructure workflows provides the most developer value. Those are all great places to choose integration with existing popular tools. At Coherence ( // I’m a cofounder) we are also building a more integrated set of tools for building software, but we don’t feel that GitHub and Slack or JIRA/Asana/linear are the tools to bite off, or that the world needs yet another CI syntax and hosting platform. build does not make sense for maximizing developer experience and value. I agree that with Space in particular, the choice of what they integrate vs. IMO it’s also about choosing the right things to integrate vs. Notifications in Mobile App sometimes not working.Ĭonfusing because why add more features that's already best served by other services? You have to type "Jetbrains space automation (keyword here)" Difficulty in writing CI/CD script due to limited documentation/knowledge on the net and unfriendly keyword ("space"? Lol. We end up creating branch for different environment. we end up creating another project just to contain wiki. So we end up creating multiple projects e.g. One project can have multiple repos, but they all share same permission. Still don't know how to integrate it lol. Issue tracker very basic, we end up using YouTrack.
CI/CD script uses Kotlin DSL, feels "heavy". We use Space due to GitLab's recent pricing changes.
0 kommentar(er)
