--- title: "Automatic deploy (chatops) with @Rultor" url: "https://www.bekk.christmas/post/2019/03/automatic-deploy-(chatops)-with-%40rultor" authors: ["Eivind Bergstøl"] published: "2019-12-03" updated: "2024-11-07T13:05:28Z" language: "en-US" type: "article" tags: ["Open source"] --- # Automatic deploy (chatops) with @Rultor The discussion of an automatic release was started many years ago, and there are several options for how to do this (none mentioned, none forgotten). Then I came across @Rultor by accident on Twitter. [no.bekk.bekkopen:NoCommons](https://github.com/bekkopen/NoCommons) is a small library for validating, generating and manipulating data typical for Norwegian domains. SSN, org-nr, names etc. And when maintaining a small, quite static, open source library like this on GitHub, we need a smooth automatic release path that is easy and fast to use when a release has to be published. Maybe I changed my computer since last time and need to restore GPG-keys, or even worse, generate new keys and distribute them. And when time goes by, a new maintainer steps up and needs to release. How was that done again? [@Rultor](http://rultor.com) is an open source robot living on GitHub. [Yegor256](https://www.yegor256.com) is the maintainer of this robot and we all can use it. Just talk to [@Rultor](http://rultor.com) in a GitHub issue and it will tell you what to do to get started. This is what I did: - Change parent-pom of project to com.jcabi:parent (not necessary, but quite convenient) - Encrypt _setting.xml_, private- and public-key (GPG) with [@Rultor](http://rultor.com) and commit them to NoCommons - Create _.rultor.yml_ and commit to NoCommons with me as _commanders_ and _architect_ [@Rultor](http://rultor.com) needs write access to the repository to publish tags and GitHub releases, so I added it as a collaborator in GitHub. Now I can comment this in an issue after merging a PR: `` @rultor release, tag=`0.9.0` `` [no.bekk.bekkopen:nocommons:0.9.0](https://github.com/bekkopen/NoCommons/releases/tag/0.9.0) Win! So now, let's look at GitHub Actions next… ## Relevant resources recommended by the author - [NoCommons](https://github.com/bekkopen/NoCommons/) - [Rultor](https://www.rultor.com/)