Skip to content
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

Adding BitBucket support #667

Closed
KOLANICH opened this issue Aug 16, 2012 · 219 comments
Closed

Adding BitBucket support #667

KOLANICH opened this issue Aug 16, 2012 · 219 comments

Comments

@KOLANICH
Copy link

KOLANICH commented Aug 16, 2012

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

@michaelklishin
Copy link
Contributor

michaelklishin commented Aug 16, 2012

Sorry, no immediate plans to do so.

@joshk
Copy link
Contributor

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
Copy link

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
Copy link
Contributor

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
Copy link

djc commented Nov 30, 2012

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

@svenfuchs
Copy link
Contributor

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"

@Potherca
Copy link

Potherca commented 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...

@rkh
Copy link
Contributor

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
Copy link

ssbarnea commented Apr 9, 2013

👍 ...for reconsidering this in the future.

@zconkle
Copy link

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.

@jacobsvante
Copy link

jacobsvante commented May 16, 2013

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

@jplehmann
Copy link

jplehmann commented May 18, 2013

+1

8 similar comments
@ottsch
Copy link

ottsch commented May 27, 2013

+1

@glarrain
Copy link

glarrain commented May 27, 2013

+1

@benburton
Copy link

benburton commented May 27, 2013

+1

@estin
Copy link

estin commented May 29, 2013

+1

@rwgrier
Copy link

rwgrier commented May 30, 2013

+1

@davidwesst
Copy link

davidwesst commented May 30, 2013

+1

@Mulkave
Copy link

Mulkave commented Jun 3, 2013

+1

@teozkr
Copy link

teozkr commented Jun 3, 2013

+1

@roidrage
Copy link
Contributor

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
Copy link

darrenpowers commented Jun 6, 2013

+1

@empperi
Copy link

empperi commented Jun 7, 2013

Definetly +1

@pekpon
Copy link

pekpon commented Jun 10, 2013

+1

1 similar comment
@willhlaw
Copy link

willhlaw commented Jun 12, 2013

+1

@likelyeatenbyagrue
Copy link

likelyeatenbyagrue commented Jun 12, 2013

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

@rweng
Copy link

rweng commented Jun 13, 2013

+1

1 similar comment
@turboladen
Copy link

turboladen commented Jun 13, 2013

+1

@PavelKonon
Copy link

PavelKonon commented Apr 21, 2014

+1

@hfossli
Copy link

hfossli commented Apr 22, 2014

+10 (devs in our company)

@robeden
Copy link

robeden commented Apr 22, 2014

+1

@lukebrowell
Copy link

lukebrowell commented 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)

@langtind
Copy link

langtind commented Apr 23, 2014

This is something we need.

+1

@aerben
Copy link

aerben commented Apr 28, 2014

+1

1 similar comment
@kode4food
Copy link

kode4food commented May 5, 2014

+1

@okev
Copy link

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
Copy link

Aaron1011 commented 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.

@Aaron1011
Copy link

Aaron1011 commented 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.

@Delors
Copy link

Delors commented May 7, 2014

+1

2 similar comments
@beshkenadze
Copy link

beshkenadze commented May 9, 2014

+1

@ajwhite
Copy link

ajwhite commented May 9, 2014

+1

@paulopatto
Copy link

paulopatto commented May 9, 2014

+💯K
👍

@VeryCB
Copy link

VeryCB commented May 14, 2014

+1

1 similar comment
@ahochsteger
Copy link

ahochsteger commented May 14, 2014

+1

@mituldthakkar
Copy link

mituldthakkar commented May 16, 2014

+1 :)

@wyuenho
Copy link

wyuenho commented May 16, 2014

+1

5 similar comments
@treshugart
Copy link

treshugart commented May 20, 2014

+1

@tscheepers
Copy link

tscheepers commented May 21, 2014

+1

@digitaljerry
Copy link

digitaljerry commented May 22, 2014

+1

@anacrolix
Copy link

anacrolix commented May 23, 2014

👍

@theScud
Copy link

theScud commented May 24, 2014

+1

@leite
Copy link

leite commented May 25, 2014

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

@mbroadst
Copy link

mbroadst commented May 26, 2014

+1

3 similar comments
@pavelnikonorov
Copy link

pavelnikonorov commented May 26, 2014

+1

@limonte
Copy link

limonte commented Jun 2, 2014

+1

@mxnr
Copy link

mxnr commented Jun 3, 2014

+1

@travis-ci travis-ci locked and limited conversation to collaborators Jun 9, 2014
@BanzaiMan
Copy link
Contributor

BanzaiMan commented Mar 16, 2020

We've announced Bitbucket integration today!

https://blog.travis-ci.com/2020-03-16-travis-ci-bitbucket-integration

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

No branches or pull requests