How do developers interact with Barkeep for a pre-commit workflow?

[nnutter]

You mention that Barkeep works for both pre-commit and post-commit workflows. You also mention that the web app fetches from a Git repo. Do you also have the ability to push to it (like Gerrit)? How would a pre-commit workflow work?

[dmac]

Barkeep is decoupled from your git repository by design, so you don't push directly to it. If you wanted to use a pre-commit workflow, one way to build that with Barkeep might be to always push to non-master remote branches, then run a process that polls Barkeep for approved commits and automatically merges them into your master branch. We tried to keep Barkeep simple and modular so custom workflows could be built on top of it; for example, we check Barkeep at deploy-time for unapproved commits and prevent them from being released. If you come up with a different way to implement a pre-commit workflow we'd be interested to hear it.

[raspberryman]

I would love to see that script, dmacdougall :)

[dmac]

There's nothing particularly special about the script we use, all the interaction with the Barkeep server is bundled into the Barkeep client gem, available on rubygems. If you want to gate your deployment on unapproved commits since the last release, use barkeep unapproved old_release_branch..new_release_branch. Full docs are in the wiki.

[sumeshkanayi]

Hi All,
I am very new to Barkeep and was wondering weather it cant be integrated with Active directory or not.
Any thoughts here?