New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple remote drivers, i.e. Github and Gogs enabled #1336

Closed
kageurufu opened this Issue Nov 20, 2015 · 6 comments

Comments

Projects
None yet
5 participants
@kageurufu

kageurufu commented Nov 20, 2015

I was able to configure multiple remotes in a prior version, and with the new configuration model.

After looking in

switch driver {
, it seems this functionality has been removed.

Is this on the roadmap for the future?

@bradrydzewski

This comment has been minimized.

Member

bradrydzewski commented Nov 20, 2015

The decision was made to remove multiple remotes and there are no plans to re-introduce. With each release Drone integrates more deeply with systems like GitHub (Gogs, etc). The more deeply we integrate with these systems the more difficult it became to support multiple remotes.

The multiple remote implementation in the prior version wasn't very good. You had to logout and login with a different account to switch between GitHub and Bitbucket (for example). The complexity caused by multiple remotes just didn't seem to justify our half-baked implementation.

Luckily Drone has a pretty lightweight runtime (< 20MB RAM) so the recommended approach is to run two drone instances on the same server with subdomains (ie drone.myompany.com and drone.gogs.mycompany.com)

@kageurufu

This comment has been minimized.

kageurufu commented Nov 20, 2015

Makes sense to me, albeit being slightly dissapointing :)

I'll just get another instance up then.

Thanks!

On Fri, Nov 20, 2015 at 9:58 AM Brad Rydzewski notifications@github.com
wrote:

The decision was made to remove multiple remotes and there are no plans to
re-introduce. With each release Drone integrates more deeply with systems
like GitHub (Gogs, etc). The more deeply we integrate with these systems
the more difficult it became to support multiple remotes.

The multiple remote implementation in the prior version wasn't very good.
You had to logout and login with a different account to switch between
GitHub and Bitbucket (for example). The complexity caused by multiple
remotes just didn't seem to justify our half-baked implementation.

Luckily Drone has a pretty lightweight runtime (< 20MB RAM) so the
recommended approach is to run two drone instances on the same server with
subdomains (ie drone.myompany.com and drone.gogs.mycompany.com)


Reply to this email directly or view it on GitHub
#1336 (comment).

@axel22

This comment has been minimized.

axel22 commented Dec 5, 2015

For what it's worth, +1 for allowing the same drone instance to connect to multiple hosting services.
Bitbucket has free private repos, but GitHub is nicer to use, so I can imagine many people splitting their repos across the two providers.

@davidak

This comment has been minimized.

davidak commented Jan 26, 2016

We also use Gitlab in the company.
This feature should get implemented some time in the future.

@tboerger

This comment has been minimized.

Member

tboerger commented Jan 26, 2016

I don't think that it's worth it to add all the overhead for multiple remotes. It's quite easy to start an instance per remote. The only thing that needs to be implemented is the behavior to get drone running in a subfolder instead of requireing a subdomain for each instance.

@bradrydzewski

This comment has been minimized.

Member

bradrydzewski commented Jan 30, 2016

please see #1336 (comment) which describes why multiple remotes were removed in 0.4, and the suggested workaround. There are no plans to re-add multiple remotes in a future release.

@drone drone locked and limited conversation to collaborators Jan 30, 2016

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