-
Notifications
You must be signed in to change notification settings - Fork 109
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
BitBucket Support #9
Comments
Any news on Bitbucket support? |
@nfuhs no news at the moment. Plans for Q1 2019 are finalized now with the main themes of AWS support and Cirrus CI Enterprise with couple of smaller improvements. Could you please share details about your use case so it can be taken into account for Q2 planning? |
Hi @fkorotkov I just was interested in Bitbucket support since I know people are using Bitbucket and Gitlab for Go projects thats all. |
Got it. Cirrus CI was design with supporting more than GitHub in mind. Internally most of the data objects are GitHub independent so it will be not that impossible to add Bitbucket support. Stay tuned! |
Are you planning BitBucket support with Git, Mercurial, or both? |
Initially with Git. And shortly after, you'll be able to use Mercurial, if your environment will have Mercurial pre-installed. For reference: Cirrus CI agent uses https://github.com/src-d/go-git for cloning the repositories to not have any requirements from the environment. You can even use containers with no OS with Cirrus CI. |
Well, we won't be able to use Mercurial if our repository couldn't be cloned in the first place. AFAIK Bitbucket doesn't have any kind of hg-git bridge, does it? |
Should be fine since the environment will be able to run something like |
Ahh, that should be ok then. |
Can't wait ! |
What is required from Bitbucket side to make CirrusCI clone git repo from there and report status back through their status API? |
@abitrolly nothing is required from the BitBucket side. As far as I've checked all APIs are in place. We'd like to get the support out later in Q2. We are trying to a few features out to kind of complete all features our phase 1 for Cirrus CI before starting expanding to other VCS and cloud providers. |
Is this progressing somehow and/or has it some plan? (our company is internally using bitbucket, and if ever we have some issue with CI, I would love to mention Cirrus CI as an option, but without knowing about state of bitbucket support I'm holding back for the moment (of course even with bitbucket support I'm not sure if I would be able to persuade for the switch, so this is just gathering information)). |
I'd like to bring to your attention a workaround I created to integrate Cirrus CI into GitLab pipelines: #10 (comment) Same tool (cirrus-run) may be helpful for implementing the workaround with BitBucket. |
BitBucket is no more. What was born as HG startup is now a Git hosting. There is really no reason to use it anymore when there is GitHub and GitLab. |
As the idea of support BitBucket is now closed/dead it maybe worth updating the FAQ at
This currently links to this issue as "At the moment Cirrus CI only supports GitHub via a GitHub Application. We are planning to support BitBucket next. " |
It's not dead. We are about to finish internal refactoring that will allow easily support BitBucket. We will announce Cirrus CI Enterprise in the two to three months with more details about supporting difference platforms beside github.com. Stay tuned and sorry for the wait but we wanted to do things the right way instead of duck type a solution. |
Any news on BitBucket support? |
Forget that, Bitbucket is being dead... |
No description provided.
The text was updated successfully, but these errors were encountered: