With the orchestration functionality included in Space, you can create a dev environment, connect it to your favorite JetBrains IDE, and start coding in seconds. Push(' you thinking about introducing remote development into your team or organization? JetBrains’ remote development workflow allows you to overcome the limits of local machines and slow laptops by keeping your source code safe and secure on a remote server. For our application, the first version of our automation script looks like this: job('Build and run tests') JB_SPACE_CLIENT_SECRET Maven is not (yet) a first class citizen of Space automation like Gradle, but the documentation gives examples that can be used right away. If you’re not into Kotlin yet, no worries, Space generates a “hello world” job for you and offers many examples that you can just apply and tweak for your own needs. Space automation is based on jobs implemented in Kotlin. Space.kts” Button you can get started easily. Open Space, navigate to your project and click on “Jobs” in the menu on the left.

If you’re lucky, your team hosts the source code and the package(s) of your application on JetBrains Space and you can just start working on it right away. In order to get a CI/CD pipeline, if you’re not so lucky you need to create a ticket describing everything upfront, join a few meetings and wait some time until somebody with the right permissions starts working on it.

Now imagine that two engineers join the project and you know you’ll practice continuous integration in order to establish a best-practice of high performing teams from the beginning of your greenfield project. Let’s assume that we’ve implemented the first use cases for our backend application with some unit tests. In the previous post we learned how to push artifacts to a package repository.

Download jetbrains space docker