Adding BitBucket support #667

Closed
KOLANICH opened this Issue Aug 16, 2012 · 218 comments

Comments

Projects
None yet
@KOLANICH

Hello.
It will be very good to have BitBucket support added.

@michaelklishin

This comment has been minimized.

Show comment
Hide comment
@michaelklishin

michaelklishin Aug 16, 2012

Contributor

Sorry, no immediate plans to do so.

Contributor

michaelklishin commented Aug 16, 2012

Sorry, no immediate plans to do so.

@joshk

This comment has been minimized.

Show comment
Hide comment
@joshk

joshk Aug 16, 2012

Member

Well, the full explanation is that we do have this on our radar but the changes would be very very extensive.

We don't have a timeline for this, nor even confirmation it will go ahead.

Thanks for logging the issue, but it is best to close it for now. Sorry.

Member

joshk commented Aug 16, 2012

Well, the full explanation is that we do have this on our radar but the changes would be very very extensive.

We don't have a timeline for this, nor even confirmation it will go ahead.

Thanks for logging the issue, but it is best to close it for now. Sorry.

@djc

This comment has been minimized.

Show comment
Hide comment
@djc

djc Nov 30, 2012

Can you elaborate on what the issues are? I might be interested into hacking on code around this. It seems like just pulling repositories from Bitbucket wouldn't be that hard. We could leave authentication to not-Github out of the picture for now.

djc commented Nov 30, 2012

Can you elaborate on what the issues are? I might be interested into hacking on code around this. It seems like just pulling repositories from Bitbucket wouldn't be that hard. We could leave authentication to not-Github out of the picture for now.

@roidrage

This comment has been minimized.

Show comment
Hide comment
@roidrage

roidrage Nov 30, 2012

Member

@djc indeed just adapting the checkout itself shouldn't be that hard. but we'll need support for Bitbuckets push payload and we need to have a way to synchronize a user's repositories and permissions to them, which is what Travis' user interface is built around. There's unfortunately a lot more involved than meets the eye, but if you're interested in hacking on that, by all means, go for it! :)

Member

roidrage commented Nov 30, 2012

@djc indeed just adapting the checkout itself shouldn't be that hard. but we'll need support for Bitbuckets push payload and we need to have a way to synchronize a user's repositories and permissions to them, which is what Travis' user interface is built around. There's unfortunately a lot more involved than meets the eye, but if you're interested in hacking on that, by all means, go for it! :)

@djc

This comment has been minimized.

Show comment
Hide comment
@djc

djc Nov 30, 2012

Can you give an indication of what the relevant areas of the codebase are?

djc commented Nov 30, 2012

Can you give an indication of what the relevant areas of the codebase are?

@svenfuchs

This comment has been minimized.

Show comment
Hide comment
@svenfuchs

svenfuchs Nov 30, 2012

Member

travis-listener accepts events from Github and queues them up to rabbitmq. they are going to be picked up by apps that use service classes in travis-core.

i think a good start might be to look at travis-core and find occurrences of "Github" and "GH"

Member

svenfuchs commented Nov 30, 2012

travis-listener accepts events from Github and queues them up to rabbitmq. they are going to be picked up by apps that use service classes in travis-core.

i think a good start might be to look at travis-core and find occurrences of "Github" and "GH"

@gcmalloc gcmalloc referenced this issue in rg3/youtube-dl Dec 13, 2012

Closed

We need to move out of GH Downloads #589

@Potherca

This comment has been minimized.

Show comment
Hide comment
@Potherca

Potherca Jan 30, 2013

I'd be interested in this too. I don't really have the time (or any experience with ruby) to contribute but maybe the good folks over at Atlassian could be persuaded to put some time into this as it would benefit their product (BitBucket) to. Sadly I don't really know anyone over there...

I'd be interested in this too. I don't really have the time (or any experience with ruby) to contribute but maybe the good folks over at Atlassian could be persuaded to put some time into this as it would benefit their product (BitBucket) to. Sadly I don't really know anyone over there...

@rkh

This comment has been minimized.

Show comment
Hide comment
@rkh

rkh Jan 30, 2013

Member

The bigger issue would be that we rely on GitHub completely for user management, access control etc. I think even if all the parts in the code base would be isolated, having a single instance that serves both GitHub and BitBucket. Though if the user management etc do get abstracted and reimplemented for BitBucket, I think it wouldn't be to hard to have a second instance running. I don't think Atlasssian would be interested in contributing to Travis CI, as they have their own proprietary alternative.

Long story short: We'd love this feature, but don't have the resources to add it.

Member

rkh commented Jan 30, 2013

The bigger issue would be that we rely on GitHub completely for user management, access control etc. I think even if all the parts in the code base would be isolated, having a single instance that serves both GitHub and BitBucket. Though if the user management etc do get abstracted and reimplemented for BitBucket, I think it wouldn't be to hard to have a second instance running. I don't think Atlasssian would be interested in contributing to Travis CI, as they have their own proprietary alternative.

Long story short: We'd love this feature, but don't have the resources to add it.

@ssbarnea

This comment has been minimized.

Show comment
Hide comment
@ssbarnea

ssbarnea Apr 9, 2013

👍 ...for reconsidering this in the future.

ssbarnea commented Apr 9, 2013

👍 ...for reconsidering this in the future.

@zconkle

This comment has been minimized.

Show comment
Hide comment
@zconkle

zconkle Apr 14, 2013

Would love to see support for bitbucket added. We use Jira and use bitbucket because it integrates heavily with the atlassian product suite. As an enterprise we are definitely open to a paid, hosted solution.

zconkle commented Apr 14, 2013

Would love to see support for bitbucket added. We use Jira and use bitbucket because it integrates heavily with the atlassian product suite. As an enterprise we are definitely open to a paid, hosted solution.

@jmagnusson

This comment has been minimized.

Show comment
Hide comment
@jmagnusson

jmagnusson May 16, 2013

Please do consider this. Github is only one of many DVCS services available.

Please do consider this. Github is only one of many DVCS services available.

@jplehmann

This comment has been minimized.

Show comment
Hide comment

+1

@ottsch

This comment has been minimized.

Show comment
Hide comment

ottsch commented May 27, 2013

+1

@glarrain

This comment has been minimized.

Show comment
Hide comment

+1

@benburton

This comment has been minimized.

Show comment
Hide comment

+1

@estin

This comment has been minimized.

Show comment
Hide comment

estin commented May 29, 2013

+1

@rwgrier

This comment has been minimized.

Show comment
Hide comment

rwgrier commented May 30, 2013

+1

@davidwesst

This comment has been minimized.

Show comment
Hide comment

+1

@Mulkave

This comment has been minimized.

Show comment
Hide comment

Mulkave commented Jun 3, 2013

+1

@teozkr

This comment has been minimized.

Show comment
Hide comment

teozkr commented Jun 3, 2013

+1

@roidrage

This comment has been minimized.

Show comment
Hide comment
@roidrage

roidrage Jun 4, 2013

Member

We appreciate your +1 on this, but at this point we can't give any ETA on when we'll support BitBucket.

Member

roidrage commented Jun 4, 2013

We appreciate your +1 on this, but at this point we can't give any ETA on when we'll support BitBucket.

@darrenpowers

This comment has been minimized.

Show comment
Hide comment

+1

@empperi

This comment has been minimized.

Show comment
Hide comment
@empperi

empperi Jun 7, 2013

Definetly +1

empperi commented Jun 7, 2013

Definetly +1

@pekpon

This comment has been minimized.

Show comment
Hide comment

pekpon commented Jun 10, 2013

+1

@willhlaw

This comment has been minimized.

Show comment
Hide comment

+1

@likelyeatenbyagrue

This comment has been minimized.

Show comment
Hide comment
@likelyeatenbyagrue

likelyeatenbyagrue Jun 12, 2013

+1 as a (poor) sole dev i use bitbucket private repo... because it's free.

+1 as a (poor) sole dev i use bitbucket private repo... because it's free.

@rweng

This comment has been minimized.

Show comment
Hide comment

rweng commented Jun 13, 2013

+1

@turboladen

This comment has been minimized.

Show comment
Hide comment

+1

@cheesecake

This comment has been minimized.

Show comment
Hide comment
@cheesecake

cheesecake Jun 13, 2013

+cheesecake

+cheesecake

@davidcorne

This comment has been minimized.

Show comment
Hide comment

+1

@JSchaenzle

This comment has been minimized.

Show comment
Hide comment

+1AU

@parruc

This comment has been minimized.

Show comment
Hide comment

parruc commented Jun 22, 2013

+1

@mokevnin

This comment has been minimized.

Show comment
Hide comment

+1

@whatwho

This comment has been minimized.

Show comment
Hide comment

whatwho commented Jun 24, 2013

+1

@PanfilovDenis

This comment has been minimized.

Show comment
Hide comment
@ssbarnea

This comment has been minimized.

Show comment
Hide comment
@ssbarnea

ssbarnea Jun 26, 2013

Due to the inability to github to provide an issue voting solution, people are spamming the issues with useless comments, also spamming watcher's inboxes, ending up in people configuring "Igore this thread"... probably the same happens even with the travis-ci developers. Bye!

Due to the inability to github to provide an issue voting solution, people are spamming the issues with useless comments, also spamming watcher's inboxes, ending up in people configuring "Igore this thread"... probably the same happens even with the travis-ci developers. Bye!

@te-chris

This comment has been minimized.

Show comment
Hide comment
@te-chris

te-chris Jul 2, 2013

I hardly think all these people taking their time to show their support for this feature is useless. That's a +1 from me.

te-chris commented Jul 2, 2013

I hardly think all these people taking their time to show their support for this feature is useless. That's a +1 from me.

@slafs

This comment has been minimized.

Show comment
Hide comment
@slafs

slafs Jul 3, 2013

Is there any statistic about how many github users are watching this issue (at least available for the project owners)?

slafs commented Jul 3, 2013

Is there any statistic about how many github users are watching this issue (at least available for the project owners)?

@pminnieur

This comment has been minimized.

Show comment
Hide comment

👍

@kevmeyer

This comment has been minimized.

Show comment
Hide comment

kevmeyer commented Apr 8, 2014

+1

@poulp

This comment has been minimized.

Show comment
Hide comment

poulp commented Apr 9, 2014

+1

@andr83

This comment has been minimized.

Show comment
Hide comment

andr83 commented Apr 12, 2014

+1

@ismaelisuani

This comment has been minimized.

Show comment
Hide comment

+1

@bonomat

This comment has been minimized.

Show comment
Hide comment

bonomat commented Apr 15, 2014

+1

@KingYes

This comment has been minimized.

Show comment
Hide comment

KingYes commented Apr 15, 2014

+1

@pstch

This comment has been minimized.

Show comment
Hide comment

pstch commented Apr 16, 2014

+1

@Ephemera

This comment has been minimized.

Show comment
Hide comment

Plz.

@rvdvyver

This comment has been minimized.

Show comment
Hide comment
@rvdvyver

rvdvyver Apr 17, 2014

+3*

+2 already taken by @docteurklein

+3*

+2 already taken by @docteurklein

@qw3r

This comment has been minimized.

Show comment
Hide comment

qw3r commented Apr 18, 2014

+1

@PavelKonon

This comment has been minimized.

Show comment
Hide comment

+1

@hfossli

This comment has been minimized.

Show comment
Hide comment
@hfossli

hfossli Apr 22, 2014

+10 (devs in our company)

hfossli commented Apr 22, 2014

+10 (devs in our company)

@robeden

This comment has been minimized.

Show comment
Hide comment

robeden commented Apr 22, 2014

+1

@lukebrowell

This comment has been minimized.

Show comment
Hide comment
@lukebrowell

lukebrowell Apr 23, 2014

Please adapt.

Github is great, but Travis-CI is currently unsuitable for customers who find themselves required to avoid vendor lock-in, such as some of the serious corporates I work with.

(+27)

Please adapt.

Github is great, but Travis-CI is currently unsuitable for customers who find themselves required to avoid vendor lock-in, such as some of the serious corporates I work with.

(+27)

@langtind

This comment has been minimized.

Show comment
Hide comment
@langtind

langtind Apr 23, 2014

This is something we need.

+1

This is something we need.

+1

@aerben

This comment has been minimized.

Show comment
Hide comment

aerben commented Apr 28, 2014

+1

@kode4food

This comment has been minimized.

Show comment
Hide comment

+1

@okev

This comment has been minimized.

Show comment
Hide comment
@okev

okev May 5, 2014

While assessing other hosted CI solutions I've come to learn that there's a lot going on that the GitHub API provides. Great. There's one small but critical design-level problem in play here - if its the GitHub API, then ITS NOT GIT.

I'd be surprised if there isn't some workflow or other design level change that can't be applied to open the door to other repos. The whole idea of GIT was to be decentralized and distributed. This is clearly not respected here. Coding, even devops, is about finding solutions to problems. Heck, even the Heroku workflow is a new git destination and plenty of developers are comfortable with that. Here are some workarounds to the github API:

  • cli utilities
  • polling the repo over ssh
  • just getting devs to push to a new remote

GitHub is great, but it's not "everything git". Please provide some level of support for other toolchains.

okev commented May 5, 2014

While assessing other hosted CI solutions I've come to learn that there's a lot going on that the GitHub API provides. Great. There's one small but critical design-level problem in play here - if its the GitHub API, then ITS NOT GIT.

I'd be surprised if there isn't some workflow or other design level change that can't be applied to open the door to other repos. The whole idea of GIT was to be decentralized and distributed. This is clearly not respected here. Coding, even devops, is about finding solutions to problems. Heck, even the Heroku workflow is a new git destination and plenty of developers are comfortable with that. Here are some workarounds to the github API:

  • cli utilities
  • polling the repo over ssh
  • just getting devs to push to a new remote

GitHub is great, but it's not "everything git". Please provide some level of support for other toolchains.

@Aaron1011

This comment has been minimized.

Show comment
Hide comment
@Aaron1011

Aaron1011 May 5, 2014

@okev: There's some discussion about this near the (way) top of the issue, which you might have missed.

To summarize, the code for Travis CI is heavily structured around Github, from everything from authentication to receiving push events. Massive refactoring will be required to add BitBucket support. You can search through travis-core for gh -it's the Github API library Travis CI uses. Given the amount of time and effort involved, the Travis team feels that they can't commit to such a huge change now, or at some definite future data. You're welcome to work towards it yourself, however. Adding in abstractions around using gh is a good first step, I think.

@okev: There's some discussion about this near the (way) top of the issue, which you might have missed.

To summarize, the code for Travis CI is heavily structured around Github, from everything from authentication to receiving push events. Massive refactoring will be required to add BitBucket support. You can search through travis-core for gh -it's the Github API library Travis CI uses. Given the amount of time and effort involved, the Travis team feels that they can't commit to such a huge change now, or at some definite future data. You're welcome to work towards it yourself, however. Adding in abstractions around using gh is a good first step, I think.

@Aaron1011

This comment has been minimized.

Show comment
Hide comment
@Aaron1011

Aaron1011 May 5, 2014

Also, it would be nice if no more people added '+1' comments. There are already a ton of them, and everyone on the Travis team gets a notification when one is added. See my above comment and the top of the issue for more information.

Also, it would be nice if no more people added '+1' comments. There are already a ton of them, and everyone on the Travis team gets a notification when one is added. See my above comment and the top of the issue for more information.

@Delors

This comment has been minimized.

Show comment
Hide comment

Delors commented May 7, 2014

+1

@beshkenadze

This comment has been minimized.

Show comment
Hide comment

+1

@ajwhite

This comment has been minimized.

Show comment
Hide comment

ajwhite commented May 9, 2014

+1

@paulopatto

This comment has been minimized.

Show comment
Hide comment
@paulopatto

paulopatto May 9, 2014

+💯K
👍

+💯K
👍

@VeryCB

This comment has been minimized.

Show comment
Hide comment

VeryCB commented May 14, 2014

+1

@ahochsteger

This comment has been minimized.

Show comment
Hide comment

+1

@mituldthakkar

This comment has been minimized.

Show comment
Hide comment

+1 :)

@wyuenho

This comment has been minimized.

Show comment
Hide comment

wyuenho commented May 16, 2014

+1

@treshugart

This comment has been minimized.

Show comment
Hide comment

+1

@tscheepers

This comment has been minimized.

Show comment
Hide comment

+1

@digitaljerry

This comment has been minimized.

Show comment
Hide comment

+1

@anacrolix

This comment has been minimized.

Show comment
Hide comment

👍

@theScud

This comment has been minimized.

Show comment
Hide comment

theScud commented May 24, 2014

+1

@leite

This comment has been minimized.

Show comment
Hide comment
@leite

leite May 25, 2014

+1, it's just an api - c'mon!

leite commented May 25, 2014

+1, it's just an api - c'mon!

@mbroadst

This comment has been minimized.

Show comment
Hide comment

+1

@jacksonfm

This comment has been minimized.

Show comment
Hide comment

+1

@limonte

This comment has been minimized.

Show comment
Hide comment

limonte commented Jun 2, 2014

+1

@mxnr

This comment has been minimized.

Show comment
Hide comment

mxnr commented Jun 3, 2014

+1

@travis-ci travis-ci locked and limited conversation to collaborators Jun 9, 2014

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