DevOps Assistant in GitHub
Rultor is a DevOps team assistant.
It helps your programmers and release managers automate
routine operations (merge, deploy, and release)
with an easy-to-use intuitive chat-bot interface.
Just say @rultor hello in any of your GitHub issues and
the conversation will start.
Full documentation is at doc.rultor.com
Schema for .rultor.yml file.
Need help online? Try our Telegram group.
These blog posts may be helpful:
Watch these videos to understand what Rultor is for:
Default Docker image is
yegor256/rultor-image.
What Problems Does Rultor Solve?
Automated deployment scripts have been around for some time.
Rultor attempts to tackle the problems those scripts do not.
The first benefit of Rultor is that it gives you isolation of your deployment
script in its own virtual environment by using Docker containers.
This substantially reduces the amount of external state that could
affect your build and makes errors more easily reproducible.
Additionally, because of the way Rultor integrates with modern issue trackers,
all the logs are stored and published to the ticket on which Rultor was
mentioned, making vital information easily accessible to all developers.
Rultor performs pre-flight builds. Instead of merging into master and then
seeing if your changes broke the build or not, Rultor checks out the master
branch, applies your changes to it, then runs everything it was set up to run.
If, and only if, everything goes well, Rultor merges the changes into master.
This programmatically prevents the master from being broken by developers. Not
having to worry about breaking the build for everyone else has a very positive
impact on the way developers write code, increasing their productivity and
mitigating their fear of making mistakes.
Lastly, Rultor provides an integrated and humanized interface to DevOps tools,
as a human-readable sentence suffices to trigger a merge or a release.
How Does Rultor Work?
Once Rultor finds a merge command
in one of your GitHub pull requests, it does exactly this:
- Reads the .rultor.yml
YAML configuration file from the root directory of your repository.
- Gets automated build execution command from it, for example
bundle test.
- Checks out your repository into a temporary directory on one of its servers.
- Merges pull request into
master branch.
- Starts a new Docker container and runs the build execution command,
for example
bundle test.
- If everything is fine, pushes modified
master branch to GitHub.
- Reports back to you, in the GitHub pull request.
You can see it in action, for example, in this pull request:
jcabi/jcabi-github#878.