Support for Multi-Repository Builds in Space Automation

Support for Multi-Repository Builds in Space Automation

Support for Multi-Repository Builds in Space Automation. In this blog post, you will learn: A job can now check out any repository within the project (not just the one that contains the running Automation script). Automation can now trigger a job run on changes in a certain repository, branch, directory, or file.

Space Automation (a part of  JetBrains Space responsible for CI/CD) recently gained a couple of cool new features that let your Automation scripts work with several Git repositories.

Here’s what’s changed, in a nutshell:

  1. A job can now check out any repository within the project (not just the one that contains the running Automation script).
  2. Automation can now trigger a job run on changes in a certain repository, branch, directory, or file.

Where this might be helpful? For example, you have a project based on microservices (each in a separate repo) and you have a separate repo with integration tests that run against the project as a whole. Another real-life example: a project consists of multiple repos and each repo has its own doc/ folder with documentation. Using Automation, you can set up a job that tracks changes in the doc/ folders of all these repositories and builds and deploys an internal documentation website.

Read on for more details!

how-to's ci/cd git newsletter

Bootstrap 5 Complete Course with Examples

Bootstrap 5 Tutorial - Bootstrap 5 Crash Course for Beginners

Nest.JS Tutorial for Beginners

Hello Vue 3: A First Look at Vue 3 and the Composition API

Building a simple Applications with Vue 3

Deno Crash Course: Explore Deno and Create a full REST API with Deno

How to Build a Real-time Chat App with Deno and WebSockets

Convert HTML to Markdown Online

HTML entity encoder decoder Online

Serverless CI/CD on the AWS Cloud

To set up a serverless CI/CD pipeline in your AWS environments, there are several key services that you need to use. Find out more here.

Travis CI vs Jenkins: Which CI/CD Tool Is Right For You?

The ultimate showdown between Travis CI vs Jenkins. Check out this guide to know who wins the race! Travis CI and Jenkins are both popular CI/CD tools and were launched in the same year i.e. 2011. As of July 2020, Jenkins has been the more obvious choice as CI/CD tool with 15.9k stars & 6.3k forks, in comparison to TravisCI which has 8k stars & 756 forks. However, these numbers alone don’t imply which CI/CD tool is more suitable for your upcoming or existing project. Jenkins is an open-source & Travis CI is free for open-source projects.

Appsinvo : What is CI & CD in Product Development?

In the last few years, technology has grown very much and reached some unprecedented levels. Similarly, the same can also be said for software development, it forms a significant part of the technology department.

Best Practices for Using Git

Git has become ubiquitous as the preferred version control system (VCS) used by developers. Using Git adds immense value especially for engineering teams where several developers work together since it becomes critical to have a system of integrating everyone's code reliably.

7 Best Practices in GIT for Your Code Quality

Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Check out 7 best practices for Git.There is no doubt that Git plays a significant role in software development. It allows developers to work on the same code base at the same time. Still, developers struggle for code quality.