Commit 02d4d7ec authored by Takuya Noguchi's avatar Takuya Noguchi 🇯🇵

Fix typo: s/BitBucket/Bitbucket/g

Signed-off-by: Takuya Noguchi's avatarTakuya Noguchi <takninnovationresearch@gmail.com>
parent a8029131
......@@ -420,7 +420,7 @@
links:
- url: https://github.com/svtek/serverless-microsoft-teams-gitlab-connector
title: Serverless Microsoft Teams Connector
- title: Autosync BitBucket - GitLab by Unito
- title: Autosync Bitbucket - GitLab by Unito
content: Simplify bug management between repos. Powerful filters can sync a few issues or the whole repo!
links:
- url: https://unito.io/sync/gitlabcom/bitbucket?utm_source=gitlab&utm_medium=marketplace&utm_campaign=&utm_content=bitbucket
......
......@@ -1227,7 +1227,7 @@ features:
gogs: true
bamboo: false
- title: "The most comprehensive import feature set"
description: "GitLab can import projects and issues from more sources (GitHub, BitBucket, Google Code, FogBugz, Gitea and from any git URL) than GitHub or any other VCS. We even have you covered for your move from SVN to Git with comprehensive guides and documentation."
description: "GitLab can import projects and issues from more sources (GitHub, Bitbucket, Google Code, FogBugz, Gitea and from any git URL) than GitHub or any other VCS. We even have you covered for your move from SVN to Git with comprehensive guides and documentation."
link_description: "Making it easier to get up and running with GitLab"
link: https://docs.gitlab.com/ee/user/project/import/index.html
category:
......
......@@ -304,7 +304,7 @@ features:
With GitLab 11.2, it is now possible to import your projects from Bitbucket Server to GitLab
with minimal effort. All that is required is to provide the server URL and your credentials.
GitLab then lists all your BitBucket Server repositories, ready for import.
GitLab then lists all your Bitbucket Server repositories, ready for import.
- name: "Private profiles"
available_in: [core, starter, premium, ultimate]
......
......@@ -129,7 +129,7 @@ With a great team make a popular next generation product that grows revenue.
* Security: Vulnerability testing. Conduct external testing. => Done.
* Security: Improve security practices through people and processes. Backlog of security issues reduced by 50% (currently 148 issues in [gitlab-ce](https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=security), 9 in [gitlab-ee](https://gitlab.com/gitlab-org/gitlab-ee/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=security), 69 on [infrastructure](https://gitlab.com/gitlab-com/infrastructure/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=security)). => Not done, backlog is larger.
* CEO: Increased usage of idea to production. 100% growth
* CMO: Generate more company and product awareness including [overtake BitBucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab). => [Acheived.](https://trends.google.com/trends/explore?date=2017-06-01%202017-09-30&q=bitbucket,gitlab)
* CMO: Generate more company and product awareness including [overtake Bitbucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab). => [Acheived.](https://trends.google.com/trends/explore?date=2017-06-01%202017-09-30&q=bitbucket,gitlab)
* VP Prod: Issue boards usage increase. 100% (.com and usage ping) => ~100% increase
* VP Prod: Service Desk usage increase. 100% (.com and usage ping) => ~1000-2000% increase
* VP Prod: Subgroups usage increase. 100% (.com and usage ping)
......
......@@ -189,7 +189,7 @@ title: "Calendar Year 2017 Q4 OKRs"
* MSD: $600K in self serve revenue. => 98% achievement.
* MSD: Grow followers by 20% through proactive sharing of useful and interesting information across our social channels. => 40% achievement of target.
* MSD: Grow number of opt-in subscribers to our newsletter by 20%. => Achieved. Grew 47.84%
* CMO: Generate more company and product awareness including increasing lead over [BitBucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab) => Achieved. GitLab = 65; BitBucket = 60.
* CMO: Generate more company and product awareness including increasing lead over [Bitbucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab) => Achieved. GitLab = 65; Bitbucket = 60.
* MSD: Implement SEO/PPC program to drive increase in number of free trials by 20% compared to last quarter, increase number of contact sales requests by 22% compared to last quarter, increase amount of traffic to about.gitlab.com by 9% compared to last quarter => 34% increase in trial request leads; 21% increase in contact request leads; 7% growth QoQ on about.gitlab.com.
* CMO: PR - October Announcements - 10.0, Series C, Wave, CLA => Done!
* CMO: AR - v10 briefing sweep for targeted analysts => Meetings secured for Q1.
......
......@@ -243,7 +243,7 @@ title: "Calendar Year 2018 Q1 OKRs"
* PMM: Plan and execute IBM Think corporate event.
* PMM: Plan and execute GTM for acquisitions and partner launches.
* PMM: Generate a customer persona map and 3 customer persona profiles.
* CMO: Generate more company and product awareness including increasing lead over [BitBucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab).
* CMO: Generate more company and product awareness including increasing lead over [Bitbucket in Google Trends](https://trends.google.com/trends/explore?q=bitbucket,gitlab).
* MSD: Implement SEO/PPC program to drive increase in number of free trials by 20% compared to last quarter, increase number of contact sales requests by 22% compared to last quarter, increase amount of traffic to about.gitlab.com by 9% compared to last quarter.
* CMO: PR - G1, G2, T1 announcements.
* CMO: AR - conduct intro briefings with all key Gartner analysts to include reviewing new positioning.
......
......@@ -37,7 +37,7 @@ title: "Atlassian Bamboo"
{:toc}
## Summary
Bamboo Server is a CI/CD solution which is part of the Atlassian suite of developer tools. It is available only in a self-managed configuration and is a closed source solution. Bamboo offers build, test, and deployment automation, and has tight integrations to Atlassian BitBucket (for SCM) and Fisheye (for understanding how source code has changed), as well as integrations to over 150 other tools. In contrast, GitLab offers a git-based SCM, SCM integrations, and code change traceability out of the box in a single application.
Bamboo Server is a CI/CD solution which is part of the Atlassian suite of developer tools. It is available only in a self-managed configuration and is a closed source solution. Bamboo offers build, test, and deployment automation, and has tight integrations to Atlassian Bitbucket (for SCM) and Fisheye (for understanding how source code has changed), as well as integrations to over 150 other tools. In contrast, GitLab offers a git-based SCM, SCM integrations, and code change traceability out of the box in a single application.
Bamboo offers a GUI for defining build plans, but does not offer pipeline as code. Bamboo also offers deployment plans (which include the notion of environments and releases), pre-deployment visibility, and per-environment deployment permissions. GitLab also offers release tracking across environments and deep visibility into the changes in a deployment, but sets deployment permissions based on branch permissions.
......@@ -61,7 +61,7 @@ Bamboo steps can be run in parallel across agents, and those agents can be auto-
- From Twitter:
- "we have also started using GitLab (moving from our own BitBucket/Bamboo servers). The CI/CD is definitely an improvement but I'm not sold on the code review features of GitLab"
- "we have also started using GitLab (moving from our own Bitbucket/Bamboo servers). The CI/CD is definitely an improvement but I'm not sold on the code review features of GitLab"
[https://twitter.com/carrchr/status/1003651960099176448](https://twitter.com/carrchr/status/1003651960099176448)
- "Sweet. Unlike Atlassian's Bamboo, @GitLab CI supports "[ci skip]" out of the box. #gitlab #devtools #success"
......
---
layout: markdown_page
title: "Atlassian BitBucket"
title: "Atlassian Bitbucket"
---
<!-- This is the template for defining sections which will be included in a tool comparison page. This .md file is included in the top of the page and a table of feature comparisons is added directly below it. This template provides the sections which can be included, and the order to include them. If a section has no content yet then leave it out. Leave this note in tact so that others can see where new sections should be added.
......@@ -46,15 +46,15 @@ GitLab is a single application for the complete DevOps lifecycle with built-in p
GitLab also offers a "prem" self-managed and "cloud" SaaS solution. GitLab runs the same exact code on it's SaaS platform that it offers to it's customers. This means customers can migrated from self-hosted to SaaS and back relatively easily and each solution maintains feature parity.
## Weaknesses
* Extending the native functionality of BitBucket is done through plugins. Plugins are expensive to maintain, secure, and upgrade. In contrast, GitLab is [open core](https://about.gitlab.com/2016/07/20/gitlab-is-open-core-github-is-closed-source/) and anyone can contribute changes directly to the codebase, which once merged would be automatically tested and maintained with every change.
* Extending the native functionality of Bitbucket is done through plugins. Plugins are expensive to maintain, secure, and upgrade. In contrast, GitLab is [open core](https://about.gitlab.com/2016/07/20/gitlab-is-open-core-github-is-closed-source/) and anyone can contribute changes directly to the codebase, which once merged would be automatically tested and maintained with every change.
## Comments/Anecdotes
* Evidence that BitBucket Cloud and BitBucket Server/Data Center are two different products and Atlassian is focused on the cloud one:
* From Atlassian themselves, BitBucket Cloud and BitBucket Server are different architectures (ie. code bases) and diverging in functionality. This is more or less spelled out in their [BitBucket Rebrand FAQ (updated Jan 2018)](https://confluence.atlassian.com/bitbucketserver/bitbucket-rebrand-faq-779298912.html?_ga=2.68100121.980444013.1542263978-1592705151.1523946360)
* Evidence that Bitbucket Cloud and Bitbucket Server/Data Center are two different products and Atlassian is focused on the cloud one:
* From Atlassian themselves, Bitbucket Cloud and Bitbucket Server are different architectures (ie. code bases) and diverging in functionality. This is more or less spelled out in their [Bitbucket Rebrand FAQ (updated Jan 2018)](https://confluence.atlassian.com/bitbucketserver/bitbucket-rebrand-faq-779298912.html?_ga=2.68100121.980444013.1542263978-1592705151.1523946360)
* From a recent [HackerNews article](https://news.ycombinator.com/item?id=17909454)
>Atlassian wants you to move to their cloud product, it's that simple. Server is a thing that makes their life harder and stops them from extracting maximum revenues from you so you can expect a soft but persistent push to switch to cloud which will get harder over time.
* Disparity between BitBucket Server and BitBucket Cloud for a top customer requested feature took Atlassian over 2 years to acknowledge. Customers found out the feature existed in Server but not Cloud once moving to Cloud. [Still not resolved as of Q4 2018](https://bitbucket.org/site/master/issues/12833/branching-models-for-bb-cloud#comment-45982415)
* [An analysis of BitBucket Server](https://docs.google.com/spreadsheets/d/1BnxRkNKytRcEnKqlnCyJFy_B6swjGyLdcwGi9bg32PY/edit#gid=0) new features per release and feature-to-maintenance ratio, per release since it was changed from Stash Server, shows a downward trend in innovation ([Data derived from Atlassian BitBucket Server Release Notes](https://confluence.atlassian.com/alldoc/bitbucket-server-documentation-directory-278071997.html))
* Disparity between Bitbucket Server and Bitbucket Cloud for a top customer requested feature took Atlassian over 2 years to acknowledge. Customers found out the feature existed in Server but not Cloud once moving to Cloud. [Still not resolved as of Q4 2018](https://bitbucket.org/site/master/issues/12833/branching-models-for-bb-cloud#comment-45982415)
* [An analysis of Bitbucket Server](https://docs.google.com/spreadsheets/d/1BnxRkNKytRcEnKqlnCyJFy_B6swjGyLdcwGi9bg32PY/edit#gid=0) new features per release and feature-to-maintenance ratio, per release since it was changed from Stash Server, shows a downward trend in innovation ([Data derived from Atlassian Bitbucket Server Release Notes](https://confluence.atlassian.com/alldoc/bitbucket-server-documentation-directory-278071997.html))
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<body><center>
<a href="/devops-tools/bitbucket/bitbucket_new_feature_graph.png" target="_blank">
......@@ -67,7 +67,7 @@ GitLab also offers a "prem" self-managed and "cloud" SaaS solution. GitLab runs
## Resources
* [Atlassian BitBucket Website](https://bitbucket.org/product)
* [Atlassian Bitbucket Website](https://bitbucket.org/product)
## Pricing
- [Bitbucket Cloud](https://bitbucket.org/product/pricing?tab=#tab-5834cfd9-fbc0-4f21-ae10-65832598b12a)
......@@ -75,7 +75,7 @@ GitLab also offers a "prem" self-managed and "cloud" SaaS solution. GitLab runs
* Standard tier - $2/user/month (min $10/month) - Same as Free + 500 build mins/month + 5GB file storage/month
* Premium tier - $5/usr/month (min $25/month) - Standard + some advanced features + 1000 build mins/month + 10GB file storage/month
- [BitBucket Server / Data Center](https://bitbucket.org/product/pricing?tab=#tab-db2f88e8-2388-4417-8e4f-6a7205437cc7)
- [Bitbucket Server / Data Center](https://bitbucket.org/product/pricing?tab=#tab-db2f88e8-2388-4417-8e4f-6a7205437cc7)
* Server - starting $2k perpetual (25 users, ppu drops roughly every 2x previous tier), includes year maintenance, single server, unlimited priv+pub repos
* Data Center - $1800/yr (25 users , ppu drops roughly every 2x previous tier) includes annual maintenance, Server + HA, DR, mirroring, SAML 2.0
* Must buy Data Center if over 2k users.
......
......@@ -62,7 +62,7 @@ But we want to make a our hybrid model work for the following reasons:
1. We want to keep being a [good steward of the open source project](/company/stewardship/).
1. The lower two tiers are a scalable way to create future customers.
1. If organization are already using Atlassian JIRA we want to be competitive with BitBucket on pricing. If they buy BitBucket it is hard for us to win them back. If they buy GitLab they discover that it can replace JIRA and over time they might buy a higher tier.
1. If organization are already using Atlassian JIRA we want to be competitive with Bitbucket on pricing. If they buy Bitbucket it is hard for us to win them back. If they buy GitLab they discover that it can replace JIRA and over time they might buy a higher tier.
Raising the price of the lowest tier will prevent people from starting with GitLab.
It will raise short term revenue at the expense of our long term market-share.
......@@ -70,7 +70,7 @@ Instead of raising prices we should focus on communicating the value of the high
This will get easier over time when we introduce more features.
In 2016 sales people focussed on free vs. starter, in 2018 on starter vs. premium, hopefully in 2020 on premium vs. ultimate.
Charging $8 for the lowest tier and discounting aggressively when we're up against BitBucket doesn't work. It is unfair to customer that are not aware of this discount and most customer are self-serve, we never talk to them.
Charging $8 for the lowest tier and discounting aggressively when we're up against Bitbucket doesn't work. It is unfair to customer that are not aware of this discount and most customer are self-serve, we never talk to them.
You can also check the viability of the different tiers by the conversion from tier to tier.
For example if 5% of users upgrade from free to starter, starter to premium, and premium to ultimate your prices are balanced.
......
......@@ -52,7 +52,7 @@ From [https://docs.gitlab.com/ee/ci/](https://docs.gitlab.com/ee/ci/)
## Competitor Scope - Continuous Integration
|Feature |GitLab |Circle CI |TFS/VSTS |Jenkins |Travis CI |BitBucket |
|Feature |GitLab |Circle CI |TFS/VSTS |Jenkins |Travis CI |Bitbucket |
|:-----------------|:----------:|:----------:|:----------:|:----------:|:----------:|:-----------:|
|Auto-scaling |Y |Y |N |N |Y |Y |
|Pipeline graphs |Y |Y |Y |Integration |N |Integration |
......@@ -62,7 +62,7 @@ From [https://docs.gitlab.com/ee/ci/](https://docs.gitlab.com/ee/ci/)
## Competitor Scope - Continuous Delivery/Deployment
|Feature |GitLab |Circle CI |TFS/VSTS |Jenkins |Travis CI |BitBucket |
|Feature |GitLab |Circle CI |TFS/VSTS |Jenkins |Travis CI |Bitbucket |
|:-----------------|:----------:|:----------:|:----------:|:----------:|:----------:|:-----------:|
|Environments |Y |N |Y |N |Y |Y |
|Env History |Y |N |N |N |N |Y |
......
......@@ -60,7 +60,7 @@ title: "DevOps tools"
### Source code management
- [GitHub](./github/)
- [Atlassian BitBucket](bitbucket/)
- [Atlassian Bitbucket](bitbucket/)
- [Microsoft TFS/VSTS/Azure DevOps](vsts/)
- [CA Technologies / Rally](https://www.ca.com/us.html)
- IBM Rational Clear case
......@@ -100,7 +100,7 @@ title: "DevOps tools"
- [Jenkins](jenkins/)
- [Travis CI](https://travis-ci.org/)
- [Atlassian Bamboo](bamboo/)
- [Atlassian BitBucket](bitbucket/)
- [Atlassian Bitbucket](bitbucket/)
- [CircleCI](https://circleci.com/)
- [Microsoft TFS/VSTS/Azure DevOps](vsts/)
- [CodeFresh](codefresh/)
......@@ -138,7 +138,7 @@ title: "DevOps tools"
- [Go CD](https://www.gocd.org/index.html)
- [Puppet Pipelines](https://puppet.com/products/puppet-pipelines)
- [Cloudbees Codeship](https://codeship.com/)
- [Atlassian BitBucket](bitbucket/)
- [Atlassian Bitbucket](bitbucket/)
- [Electric Cloud ElectricFlow](http://electric-cloud.com/products/electricflow/)
- [CA Technologies](https://www.ca.com/us.html)
- [XebiaLabs](https://xebialabs.com/)
......
......@@ -55,9 +55,9 @@ A: We are running a promotion that makes this feature available (normally a Silv
A: Yes
### Q: Does GitLab CI/CD also integrate with BitBucket? Other solutions?
### Q: Does GitLab CI/CD also integrate with Bitbucket? Other solutions?
A: Yes, but the process is more manual. GitLab CI/CD can connect to any git repo via URL, including BitBucket, and configure status webhooks manually. Docs on how to [manually enable GitLab CI/CD.](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/bitbucket_integration.html) (With GitHub the process is all automatic.)
A: Yes, but the process is more manual. GitLab CI/CD can connect to any git repo via URL, including Bitbucket, and configure status webhooks manually. Docs on how to [manually enable GitLab CI/CD.](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/bitbucket_integration.html) (With GitHub the process is all automatic.)
### Q: How does GitLab CI/CD integration to GitHub work?
......@@ -122,7 +122,7 @@ Cons:
- Developers won't have access to artifacts, pipelines output traces, registry images, or security reports.
#### Do they need users for each developer using GitHub/BitBucket - why/why not?
#### Do they need users for each developer using GitHub/Bitbucket - why/why not?
No - It’s not necessary, but enabling developers grants benefits:
......
......@@ -17,7 +17,7 @@ title: "Sales Training"
- CST202 [Hosting Gitlab in the Cloud](https://www.youtube.com/watch?v=1OLCDtUkw0Q&index=2&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
- CST203 [Integrating Atlassian and GitLab](https://www.youtube.com/watch?v=o7pnh9tY5LY&index=3&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
- CST204 [GitLab Maintenance and Support](https://www.youtube.com/watch?v=X8jsj59b4vk&index=4&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
- CST205 [We already use JIRA, so shouldn't we go with BitBucket?](https://www.youtube.com/watch?v=-JRab22h9Dg&index=5&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
- CST205 [We already use JIRA, so shouldn't we go with Bitbucket?](https://www.youtube.com/watch?v=-JRab22h9Dg&index=5&list=PLFGfElNsQthbFw3QxWjoTsDMoLmZx1SbP)
- CST206 [Traditional DevOps Dasiy Chain](https://www.youtube.com/watch?v=YHznYB275Mg)
......
......@@ -45,7 +45,7 @@ To learn more, see the [Solutions Architect handbook](/handbook/customer-success
* System Logging
* Experience with several of the following tools preferred:
* Ruby on Rails, Java, PHP, Python
* Git, BitBucket, GitHub, SVN
* Git, Bitbucket, GitHub, SVN
* Jira, VersionOne, TFS
* Jenkins, Travis, CircleCI
* Veracode, Fortify
......
......@@ -41,7 +41,7 @@ email account, you are usually not asked to pay more to store more. Unlimited re
Price for Git repository hosting per month in popular cloud solutions
| | GitHub.com old | GitHub.com new| BitBucket.org | GitLab.com |
| | GitHub.com old | GitHub.com new| Bitbucket.org | GitLab.com |
| :--- | :---------: | :---------: | :-----------: | :--------: |
| **Personal usage** | | | |
| 1 private repo | $7 | $7 | $0 | $0
......
......@@ -512,7 +512,7 @@ The APIs are all written using Grape. They have the [GitLab CE][ce] project sepa
They also forked [Omnibus][omn] in order to be able to package the CE Rails project as a ".deb". Everything is orchestrated with Docker. And when a new version is available, you only need to `apt-get update && apt-get ugprade` and it will do all the work of backing up and migrating Postgresql, updating the code, bundling in new dependencies, restarting the services and so forth. It's super convenient and you should take a look at this project if you have complicated Rails deployments into your own infrastructure (out of Heroku, for example).
I am almost done moving hundreds of repositories from both BitBucket and GitHub to GitLab right now and the developers from my company are already using it in a daily basis without any problems. We are almost at the point where we can disengage from BitBucket, GitHub and external CIs.
I am almost done moving hundreds of repositories from both Bitbucket and GitHub to GitLab right now and the developers from my company are already using it in a daily basis without any problems. We are almost at the point where we can disengage from Bitbucket, GitHub and external CIs.
You will be surprised how **easy your company can do it** too and **save a couple thousand dollars** in the process, while **having fun doing it**!
......
......@@ -22,7 +22,7 @@ But one thing that was missing was that you couldn't use GitLab CI/CD with GitHu
{:.intro-header}
While GitLab works best when you use it [all end-to-end](/handbook/product/single-application/), we also seek to [play well with others](/direction/#plays-well-with-others). In this spirit, we’ve added [CI/CD integration with GitHub](/features/github), and more generally the ability
to [integrate CI/CD with other external repos](#gitlab-cicd-for-external-repos) like BitBucket as well. We see four primary audiences that this functionality is designed for. 
to [integrate CI/CD with other external repos](#gitlab-cicd-for-external-repos) like Bitbucket as well. We see four primary audiences that this functionality is designed for. 
### Open source projects
{:.intro-header-h3}
......
......@@ -28,7 +28,7 @@ As our plans are always in draft, we'd love to hear your thoughts, and any sugge
Git's distributed design made new collaborative workflows possible, and forking has made collaboration even easier. Forking is the workflow of choice for open source, and for the same reasons it is also great for private organizations. We want to remove the barriers to collaboration and [inner sourcing](/2016/07/07/trends-version-control-innersourcing/), but also make it easier to collaborate with external open source projects too.
The distributed capabilities of Git aren't limited to a single server. Open source software is used extensively in commercial applications of all kinds, but collaboration between open source projects and commercial is difficult. Features and bug fixes to open source projects can sit in stale forks in private Git repositories for lack of tools and process. [Distributed merge requests](https://gitlab.com/groups/gitlab-org/-/epics/260) will make it easy publish a patch from a private GitLab instance to a public upstream server, be it GitLab, GitHub or BitBucket. Teams will be able to work on a patch privately following internal processes, but instead of merging the reviewed and tested change privately, it can be published to a new public merge request upstream. Contributing fixes and features upstream isn't only good for the community, but it also makes commercial sense by eliminating the costly task of keeping a stale, private fork up to date. We want to make it easy for everyone to contribute to open source software, as individuals and as companies!
The distributed capabilities of Git aren't limited to a single server. Open source software is used extensively in commercial applications of all kinds, but collaboration between open source projects and commercial is difficult. Features and bug fixes to open source projects can sit in stale forks in private Git repositories for lack of tools and process. [Distributed merge requests](https://gitlab.com/groups/gitlab-org/-/epics/260) will make it easy publish a patch from a private GitLab instance to a public upstream server, be it GitLab, GitHub or Bitbucket. Teams will be able to work on a patch privately following internal processes, but instead of merging the reviewed and tested change privately, it can be published to a new public merge request upstream. Contributing fixes and features upstream isn't only good for the community, but it also makes commercial sense by eliminating the costly task of keeping a stale, private fork up to date. We want to make it easy for everyone to contribute to open source software, as individuals and as companies!
![Mockup of distributed merge request widget](/images/blogimages/merge-request-distributed.png){: .medium.center.shadow}
......
......@@ -19,7 +19,7 @@ GitHub just launched [free private repos with up to three collaborators](https:/
When we [originally announced GitLab.com](https://news.ycombinator.com/item?id=4428278) I made the main point that it would have private repos for free. I think it is great for beginner users that private repos on GitHub are now free.
If you're starting to program and aren't ready to share your code with the world yet, you don't have to have a paid account to keep it private.
At the time, I was very disappointed to learn that BitBucket.org already offered the same. GitLab took off despite that and GitLab.com recently surpassed [10 million projects](https://twitter.com/gitlab/status/1075377374022262784) and in the [top dev tools ranking of Axosoft](https://blog.axosoft.com/top-developer-tools-2019/) GitLab climbed the ranks 4 spots and overtook GitHub for the first year.
At the time, I was very disappointed to learn that Bitbucket.org already offered the same. GitLab took off despite that and GitLab.com recently surpassed [10 million projects](https://twitter.com/gitlab/status/1075377374022262784) and in the [top dev tools ranking of Axosoft](https://blog.axosoft.com/top-developer-tools-2019/) GitLab climbed the ranks 4 spots and overtook GitHub for the first year.
## Looking ahead
......@@ -42,4 +42,4 @@ In the meantime, here are some more details of our current GitLab free private r
| Location of the repo | Anywhere | Not in groups/orgs |
| API concurrent rate limit | 36000 | 5000 |
Sign up for a [free trial](https://about.gitlab.com/pricing/#gitlab-com)
\ No newline at end of file
Sign up for a [free trial](https://about.gitlab.com/pricing/#gitlab-com)
......@@ -31,7 +31,7 @@ extra_css:
%li SVN to GIT
%li GitHub.com
%li GitHub Enterprise
%li BitBucket
%li Bitbucket
%li Jenkins
%li GitLab Core
%li GitLab.com
......
......@@ -79,7 +79,7 @@ extra_css:
%h2 GitLab CI/CD for External Repositories
.overview
:markdown
Not only does GitLab integrate with GitHub, but you can also run CI/CD from any external git repo from any vendor by adding a repo by URL to your project and configuring webhook. For example, you can [configure BitBucket to use GitLab CI/CD](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/bitbucket_integration.html).
Not only does GitLab integrate with GitHub, but you can also run CI/CD from any external git repo from any vendor by adding a repo by URL to your project and configuring webhook. For example, you can [configure Bitbucket to use GitLab CI/CD](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/bitbucket_integration.html).
Read the documentation for [GitLab CI/CD for external repositories](https://docs.gitlab.com/ee/ci/ci_cd_for_external_repos/).
.col-md-4.hidden-xs.hidden-sm
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment