In the second part of this series, we’ll look at how we can use GitHub Actions as a build pipeline for our Gradle project.

Originally published in German at flowsquad.io.

A build pipeline of the ancient Romans — Photo by Z S on Unsplash

At the same time as GitHub Packages, GitHub Actions was announced. This service makes it possible to respond to events with different actions. Numerous different events are supported.

We have already dealt with GitHub Packages in the first part of this series. You can find it here. This part builds on the project we created in the first blog post. In this part, we will add a build pipeline with GitHub Actions to it. An artifact will be built from our Gradle project, which is then published automatically in GitHub Packages on every commit.

What is GitHub Actions?


Big challenges — little time: How we managed to work more efficiently by using the right tools.

Originally published in German at flowsquad.io.

Photo by Markus Winkler on Unsplash

Before founding our company, we all worked in various other companies. However, they all had one thing in common: the internal workflows were slow and complicated, countless emails and phone calls were required for each request, and for every problem, there were at least two different tools.

Such an environment prevents efficient working, which is essential for survival, especially in small companies and start-ups. For this reason, we have been testing a lot of different tools over the past few months. By now, we found a very delightful combination.

In this blog post, we…


In the first part of this series, we will find out how you can use GitHub Packages in your Gradle projects as your private package registry.

Originally published in German at flowsquad.io.

Photo by chuttersnap on Unsplash

Almost exactly a year ago, GitHub announced the beta for its newest product — GitHub Package Registry. It was to become the central repository for artifacts created from code already hosted by GitHub. In addition to npm, it should support Docker, Maven, NuGet, and RubyGems.

It is yet another building block in GitHub’s strategy to support the entire journey from writing code to shipping it. At the same time, GitHub Actions was announced, which we will deal with in the next part of the series.


From March 20 to 22, the WirVsVirus Hackathon took place under the sponsorship of the German Federal Government. How we were able to move from the initial idea to a prototype in less than 48 hours.

Logo of #WirVsVirus

From March 20 to 22, the WirVs virus hackathon took place all over Germany and — reflecting the current situation — entirely virtually. Under the sponsorship of the German Federal Government and Head of the Chancellery Helge Braun, more than 28,000 active participants in over 1,500 projects sought solutions to the problems arising from the COVID 19 pandemic for Germany, Europe, and the whole world. FlowSquad was part of it.

RemedyMatch: An idea is taking shape


Originally published in German at https://www.flowsquad.io

Our website at https://www.flowsquad.io

What developer hasn’t been in this situation — you just want to create a simple website and are suddenly confronted with lots and lots of technologies, providers, and solutions. And whichever you pick, sooner or later, doubts will arise, if the one you chose really is the best solution…

That’s precisely the problem we had as well. After we founded our company, we needed a website as fast as possible. But should we use one of the many available templates on the market or do everything ourselves? …

FlowSquad.io

We are experts in workflow automation and customized software development. We share our experiences with Camunda, Spring Boot, React, Apache Kafka and more!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store