Software Development

In this blog post, you'll see how the developer advocacy team at JetBrains adopted Space to make developing content in the JetBrains Guide easier.

Space makes it easy for you and your team to review code, and discuss changes. You can use any IntelliJ IDEA-based IDE to browse code reviews, assign, manage, view and submit comments, and accept changes.

In this blog post, you will learn: 1. How a job can check out any repository within the project. 2. How to trigger a job run on changes in a certain repository, branch, directory, or file.

What’s coming to Space this year? An on-premises version, video calls, external collaborators, a dark theme, Space drive, and more.

Wondering who can see the data in your Space projects, Git repositories, channels, or package repositories? Read this post to learn about how visibility works in Space.

Looking for an integrated solution for product development, distributed team collaboration, or virtual learning? Discover how you can benefit from Space based on our early adopters’ experience.

Space Automation lets you automate routine tasks that require data from other Space modules or tasks that need to integrate with external systems. Let's see how to use external libraries in Space Automation to keep your personal agenda and Space calendar synchronized.

Quality gates are a quality control technique used in collaborative software development. Though it’s quite a broad term, Space currently uses it only for merge request workflows. Simply put, a quality gate is a set of conditions that needs to be met before you can merge your commit into a protected branch (for example, the master). Let’s take a look at them in more detail. Types of quality gates

One of the best things about the Space Automation DSL is that it's based on Kotlin script. This means not only that you can use pure Kotlin inside your build scripts but also that you can reference any external .jar libraries.

During this session, JetBrains Developer Advocate Maarten Balliauw introduced many of the concepts behind Space Automation. He also discussed the automation DSL, running builds, publishing to the Space package registry, secrets and parameters, and much more! Evgeniy Koshkin, Automation Team Lead, hosted a Q&A session after Maarten’s talk.

Currently, Docker containers are the main execution environment in Space Automation. So, what can you basically run inside the containers? These are: shell scripts, arbitrary Kotlin code, and container image commands. Let's take a look at how you can do all of these.

Join us on October 6, 2020 for a free live webinar, Introduction to Automation: CI/CD in Space. Explore Space Automation concepts, and learn how you can run CI/CD activities in Space to build, test, and deploy your project.

Space Automation, one of the most popular planned features among our early adopters during the EAP, is now available to all Space Beta customers. With Automation, you can run your CI/CD activities in Space to build, test, and deploy your project.

Once again, we're extending the list of repository types supported by Space Packages. Now it's time for npm registries! Let's take a look at the basics: how you can create an npm registry, and how you can publish and get npm packages – all this right inside your Space instance.

Space Packages are receiving a number of important updates. If you're a Packages user, please read this blog post carefully. Until recently, Space Packages was an organization-wide (top-level) module, which led to some inconveniences: The Packages page showed you all repositories at once. It was not possible to filter for repositories related to a certain project. Organization-wide P

Space Packages continue evolving! In addition to creating Maven repositories and container registries, now you can create your own NuGet feeds. If you're interested, let's take a closer look. (more…)

Let's continue our series of blog posts dedicated to Space Packages. The previous post was about working with Maven repositories. In this one, let's play with container registries! What are they for? The most obvious example is a Docker registry, but in addition to Docker images, container registries support OCI images and Helm charts. The structure of the post will be quite the same: we'll show y

Today, we want to introduce you to the concept of turn-based code reviews in Space! The idea behind turn-based code reviews is to make the process of reviewing code as clear as possible for the author of the code, and the reviewers. When the Space team was looking at the typical code review process, we found two issues that could be improved: Who should take action? It's not always cle

In one of our previous blog posts, we've made an introduction to Space Packages. Now, it's time to try them in action! Let's start with Maven repositories: we'll take a look at how to create a Maven repo, log into it, and then publish the artifacts of a Gradle or Maven project. Create a repository The steps needed to do this are pretty obvious, but let’s cover them just to be sure. Open the

Teams using Git repositories in Space can setup rules to limit what contributors can do, or to enforce certain standards. Branch restrictions let us restrict who can create and delete branches, and who can (force) push to a branch. With push restrictions, we can verify committers, limit file size and file types. Let's look at a few examples! (more…)