Can jig be used as "pre-receive" or other server side commit hooks? #9

Open
mithro opened this Issue Jul 23, 2014 · 3 comments

Comments

Projects
None yet
2 participants
@mithro
Contributor

mithro commented Jul 23, 2014

Firstly, jig looks pretty awesome way to manage and write git hooks! You've done a great job of writing excellent documentation and made it very easy to use. It's also nice to see this written in Python rather than Perl, bash or ruby!

I'm interested in creating a bunch of commit hooks on the server side to enforce that the pre-commit hooks have been run/pass and a couple of other small policy things. As I'd like to run the same set of hooks at commit time and on the server side, it would be nice if we could use jig for that. All the documentation seems to only talk about the commit time hooks.

Is there any support for this? If not, how hard do you think it would be to add?

@robmadole

This comment has been minimized.

Show comment
Hide comment
@robmadole

robmadole Jul 23, 2014

Owner

I've been working on a jig ci command that will run Jig in something like https://travis-ci.org. It's not quite done yet and is a little dangerous to use because I am also fixing #3 with it. The ci branch contains this work if you're brave.

Jig doesn't support anything but the pre-commit hook right now. I'd have to think about how to design other hooks. I think it would be a pretty significant effort.

Perhaps the ci mode would work. I'll cut a release when its done and throw a comment in this thread and you can see if it might work for you. Thanks for the thoughts, Tim!

Owner

robmadole commented Jul 23, 2014

I've been working on a jig ci command that will run Jig in something like https://travis-ci.org. It's not quite done yet and is a little dangerous to use because I am also fixing #3 with it. The ci branch contains this work if you're brave.

Jig doesn't support anything but the pre-commit hook right now. I'd have to think about how to design other hooks. I think it would be a pretty significant effort.

Perhaps the ci mode would work. I'll cut a release when its done and throw a comment in this thread and you can see if it might work for you. Thanks for the thoughts, Tim!

@mithro

This comment has been minimized.

Show comment
Hide comment
@mithro

mithro Jul 23, 2014

Contributor

I don't quite understand what ci mode is for? How is it different from the normal mode?

Contributor

mithro commented Jul 23, 2014

I don't quite understand what ci mode is for? How is it different from the normal mode?

@robmadole

This comment has been minimized.

Show comment
Hide comment
@robmadole

robmadole Jul 23, 2014

Owner

It's designed to run on the server. So you'll commit the .jigplugins.txt file into the repository then when, for example, Travis CI runs the tests you could also add a command that runs jig ci .jigplugins.txt. This would automatically install the plugins and run them on the latest commits in the repository. If a plugin fails it would cause the build to fail and the CI server would notify interested parties.

Owner

robmadole commented Jul 23, 2014

It's designed to run on the server. So you'll commit the .jigplugins.txt file into the repository then when, for example, Travis CI runs the tests you could also add a command that runs jig ci .jigplugins.txt. This would automatically install the plugins and run them on the latest commits in the repository. If a plugin fails it would cause the build to fail and the CI server would notify interested parties.

@robmadole robmadole added this to the 0.3.0 milestone Feb 28, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment