summaryrefslogtreecommitdiff
path: root/lib/oxidized/hook
AgeCommit message (Collapse)Author
2016-02-25Changed configuration item namesawlx
2016-02-25Removed unnecessary repetitionawlx
2016-02-25Added support for SSH Key usage and ssh-agent-forwardingawlx
2016-02-19refactor `#remote_repo` to not rely on `#single_repo?` configDanilo Sousa
even in the case we have groups, we can assume is only one repository if the `remote_repo` config is a String.
2016-02-19move the groups remote to the hook configDanilo Sousa
thanks to @ElvinEfendi for the idea! :+1:
2016-02-19fix 'GithubRepo#single_repo?' private methodDanilo Sousa
2016-02-18create tests for `GithubRepo#validate_cfg!` methodDanilo Sousa
2016-02-18fix `githubrepo` hook for groups repositories remotesDanilo Sousa
when there was a repository per group we could not use the hook for pushing since we only had **one** remote configured. This PR configures each repository its own remote based in the `groups` config, as follows: ``` --- groups: first: remote_repo: git@gitlab.lab:oxidized/first.git second: remote_repo: git@gitlab.lab:oxidized/second.git ```
2016-01-04Merge remote-tracking branch 'upstream/master' into merge-upstreamElvin Efendi
2015-12-27expose git repo name and commit oid in hook mechanism and environment variablesNick Hilliard
2015-12-13do not commit when there is no diffElvin Efendi
2015-12-13let user configure which auth method to useElvin Efendi
2015-12-08warn when there is a conflictElvin Efendi
2015-12-07pull origin/master before pushingElvin Efendi
2015-12-04consider local repo mainElvin Efendi
2015-12-04user password username for github apiElvin Efendi
2015-11-13githubrepo hook specElvin Efendi
2015-11-13do not rescue general exceptionElvin Efendi
2015-11-13raise more specific exception when required key is not presentElvin Efendi
2015-11-13a callback to push config changes to a remote repositoryElvin Efendi
2015-09-17restore ruby 1.9.3 compatibility0.8.1Saku Ytti
fix some whitespaces bump up gemspec version
2015-08-28Initial implementation of the hook featureAnton Aksola
The current implementation is modular and allows users to define hooks in several ways: * Use one of the built-in hook types (currently only 'exec') * Define their own Hook classes inside ~/.config/oxidized/hook Exec hook type runs a user defined command with or without shell. It populates a bunch of environment variables with metadata. The command can either be run as synchronous or asynchronous. The default is synchronous.