Source: medium.com
Using babashka for GitHub ActionsCategory: Docker, Jenkins, github
Lately I had the chance to create a new GitHub Action that executes a babashka script, and since I couldn’t found a similar one in GitHub marketplace, I’ve decided to publish it to the marketplace. Please note that the purpose of this post is not to “teach” you how to create GitHub Actions and workflows (you can read more about it in the GitHub documentation) nor do I pretend to be expert of it.
TL;DR you can access the final output of this post in this GitHub repository or in the GitHub Actions marketplace.
If you used to abstract GitHub as “just” a place to host and manage your Git repositories (with some cool collaboration tools), while the rest of your development life cycle takes place somewhere else (Jenkins for CI/CD as an example) — you can now use GitHub Actions to manage many of those SDLC tasks directly in your Git repository.
With GitHub Actions, you can execute the CI jobs directly in your Git repository without using an external CI server.
TL;DR you can access the final output of this post in this GitHub repository or in the GitHub Actions marketplace.
If you used to abstract GitHub as “just” a place to host and manage your Git repositories (with some cool collaboration tools), while the rest of your development life cycle takes place somewhere else (Jenkins for CI/CD as an example) — you can now use GitHub Actions to manage many of those SDLC tasks directly in your Git repository.
With GitHub Actions, you can execute the CI jobs directly in your Git repository without using an external CI server.
Related Articles
Community Partners
DevOps Careers