Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 4.07 KB

README.rdoc

File metadata and controls

72 lines (49 loc) · 4.07 KB
Raw

Redmine Github Hook ↑

This plugin allows you to clone github repository to local automaticly and update your local Git repositories in Redmine when changes have been pushed to Github.

Description ↑

Redmine <redmine.org> has supported Git repositories for a long time, allowing you to browse your code and view your changesets directly in Redmine. For this purpose, Redmine relies on local clones of the Git repositories.

If your shared repository is on a remote machine - for example on Github - this unfortunately means a bit of legwork to keep the local, Redmine-accessible repository up-to-date. The common approach is to set up a cronjob that pulls in any changes with regular intervals and updates Redmine with them.

That approach works perfectly fine, but is a bit heavy-handed and cumbersome. The Redmine Github Hook plugin allows Github to notify your Redmine installation when changes have been pushed to a repository, triggering an update of your local repository and Redmine data only when it is actually necessary.

Installation ↑

  1. Installing the plugin

    1. Install the json gem <json.rubyforge.org/> on the machine where Redmine is running.

    2. Follow the plugin installation procedure at www.redmine.org/wiki/redmine/Plugins.

    3. Restart your Redmine.

    4. Config your local git repositories path in the plugin configuration(/settings/plugin/redmine_github_hook), pls ensure this path can be writable via redmine.

  2. Adding a Git repository to a project (note, this should work whether you want to use Redmine Github Hook or not). Just directly type “git://github.com/xxx.git”, that’s all.

## Simplyfollow the instructions at http://www.redmine.org/wiki/redmine/HowTo_keep_in_sync_your_git_repository_for_redmine

  1. Connecting Github to Redmine

    1. Go to the repository Admin interface on Github.

    2. Under “Service Hooks” add a new “Post-Receive URL” of the format: “[redmine_installation_url]/github_hook” (for example “example.com/github_hook”).

      1. By default, Github Hook assumes your Github repository name is the same as the project identifier in your Redmine installation. If this is not the case, you can specify the actual Redmine project identifier in the Post-Receive URL by using the format “[redmine_installation_url]/github_hook?project_id=” (for example “example.com/github_hook?project_id=my_project”).

That’s it. Github will now send a HTTP POST to the Redmine Github Hook plugin whenever changes are pushed to Github. The plugin then takes care of pulling the changes to the local repository and updating the Redmine database with them.

Assumptions ↑

  • Redmine 1.1 running on a *nix-like system. It will probably work on older versions as well.

  • Git 1.5 or higher available on the commandline.

History ↑

0.2.0

  • + clone github repository to local automaticly

  • + the plugin configuration page to set the local git repositores path.

  • + show the scm url in the repository page via ZhuangBiaoWei

  • + show the github url in the repository page

License ↑

Copyright © 2009 Jakob Skjerning

Copyright © 2011 Riceball LEE

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.