Aniketos is one of two gatekeepers of Mount Olympus. It also keeps your git repository from pushes that don't fit your project standards.

Imagine you have a project, and you have your coding convention setup, or even have a Jenkins job that runs a linter on every push. Now one of your colleague comes along, who isn't too familiar with the coding conventions. He checks in some code that violates the standard, pushes and breaks the build. Wouldn't it be nice if the git repository can run the linter on the pushed files, and reject the push if it's not up-to-par? This way, your colleague gets immediate feedback and can learn the conventions faster.

This is where Aniketos can help. Hate long rambling commit messages? Write a Aniketos checker that rejects those pushes. Some commits don't have a reference to a ticket? Write a Aniketos checker that rejects those pushes.

Git has this mechanism called 'hooks' which allows scripts to be executed when certain events happen to your repository. Aniketos can be used as the server update hook, which gets called before the server ref is updated.

• If you're using pip

pip install aniketos

• or with EasyInstall

easy_install aniketos

After aniketos is installed, invoke:

install-hook <repository-location>

You need write permission to repository-location. This will install aniketos to <repository-location>/hooks/update

A sample config:

[policy:mastercheckerpolicy]
type=decremental
result_filepath=/tmp/staging/master/result

[checker:masterchecker]
type=pylint
staging_dir=/tmp/staging/master/staging
policy=mastercheckerpolicy
rcfile=

[rule:refs/heads/master]
refmatch=refs/heads/master
checker=masterchecker

Git repo has the following layout:

sample.git
|-- HEAD
|-- config
|-- aniketos.ini*
|-- description
|-- hooks
|   |-- ...
|   |-- update -> /path/to/aniketos/bin/update**
|   `-- ...
|-- info
|   `-- exclude
|-- objects
|   |-- ...
|   `-- ...
`-- refs
    |-- heads
    |   `-- master
    `-- tags

The nodes with asterisks are the ones specific to aniketos.

If you have other update hooks already in the repo, say, girocco's default update hook, you will need to rename update to something else, e.g., update-girocco. Link update from aniketos to $REPO/hooks/update-aniketos, and create an entry point update hook:

#! /bin/bash
set -e

for hook in $(ls hooks/update-*); do
    "$hook" "$@"
done

Of course you need to make all of these scripts executable:

chmod +x update*

• concurrent commits