Project

General

Profile

Actions

Feature #4457

open

Support for remote Git repositories via RESTful API

Added by Alexey Palazhchenko over 14 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2009-12-21
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

It would be cool to implement support for remote Git repositories hosted on services like GitHub and Gitorious via their RESTful API.

GitHub API


Related issues

Related to Redmine - Feature #3825: Git repository via the git:// protocolClosed2009-09-05

Actions
Actions #1

Updated by André H. over 14 years ago

This would be a great feature. For now I have to work around this with a stupid cronjob that pulls all changes from Github into a local repository on the server.
+1

Actions #2

Updated by Felix Schäfer over 14 years ago

I'm not sure if you'll ever get non-generic SCM adapters in Redmine (and to be honest, I'd rather see such thrid-party integration in a plugin than in core), and quite frankly, git manages multiple shared repos very well, but you could achieve a better integration than through a cronjob with "other" git repositories through the /sys/fetch_changesets action introduced in #2925 (although I'm not sure if Redmine would do a pull for you).

Actions #3

Updated by Alexey Palazhchenko over 14 years ago

Yes, I know about cron jobs, but it's just not possible for cloud environments like Heroku.

Actions #4

Updated by Warren Postma over 7 years ago

In 2016 I think it would make more sense to just make Redmine + Gitlab interaction richer.

Gitlab has:

1. Merge request workflow.
2. It has built in issue tracker but you can turn that off and link it to Redmine so you don't have to migrate away from Redmine's rich features.
3. It has a build automation system that can automate build, test, and deploy on a multi-fork, multi-branch git repository ecosystem, something that would be hell on earth to build into Redmine.

The reason we still use redmine:

1. All our wikis are in it, and our existing artifacts (bugs, tasks, epics, sprints).
2. We want one redmine project with multiple git repos, whereas gitlab's built in bug tracker is one-set-of-issues-per-git-project.

Currently redmine's git integrations are useless to us. But a REST api interaction between Redmine and Gitlab are incredibly rich in potential, and anyone interested in collaborating on that should contact me via warren dot postma at gmail dot com

Actions #5

Updated by Warren Postma over 7 years ago

My proposal is on gitlab issues tracker here:

https://gitlab.com/gitlab-org/gitlab-ce/issues/23800

Actions

Also available in: Atom PDF