2018-03-22
Mark Pundsack
A: With GitLab CI/CD for GitHub, enterprises working with multiple different types of code repositories can now standardize on GitLab CI/CD for seamless consistency across both their GitHub and GitLab code repositories. Open source projects that host their code on GitHub can take advantage of CI/CD on GitLab SaaS, where GitLab offers top tier features for free to open source projects.
A: GitLab Brings Industry-Leading Continuous Integration and Deployment to GitHub Community
A: Sid Sijbrandij: “Continuous integration and deployment form the backbone of modern DevOps,” said Sid Sijbrandij, CEO and co-founder of GitLab. "With this new offering, businesses and open source projects that use GitHub as a code repository will have access to GitLab’s industry leading CI/CD capabilities."
A: https://about.gitlab.com/press/releases/2018-03-22-gitlab-cicd-github-integration.html
A: Yes, there are more details in the 10.6 release post [link to blog post]
A: Yes, https://about.gitlab.com/solutions/github/ [will go live 2018-03-22]
https://about.gitlab.com/solutions/github/ will also redirect to the longer URL and can be used in social, emails, etc.
A: We are running a promotion that makes this feature available (normally a Premium feature) part of the Free tier on GitLab SaaS for one year. (Self-managed customers have access in the Premium tier.)
A: Yes
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. (With GitHub the process is all automatic.)
A: GitLab users can create a CI/CD project in GitLab connected to an external GitHub code repository, which automatically prompts GitLab CI/CD to run whenever code is pushed to GitHub and post CI/CD results back to GitHub when completed.
A: The ability to easily set up GitLab CI/CD on GitHub is the main feature enabling continuous integration, security testing, container registry, CD/release automation, configuration management, and monitoring.
A: Several
With large enterprises we have 2 opportunities:
GitLab is committed to supporting open source. ON GitLab SaaS, open source projects get unlimited concurrent jobs and 50K units of compute per month for free. The GitHub Integration allows projects who host their code on GitHub to use GitLab for CI/CD for free.
By making GitLab CI/CD for GitHub available free of charge as part of our GitLab SaaS Free tier we are allowing anyone who uses GitHub.com to host their code, to use GitLab SaaS for their CI/CD. This is a way to expand the reach of GitLab and expose GitLab to users who may otherwise have not tried GitLab out.
Gemnasium customers who are using GitHub now have a migration path to use the Gemnasium features we’ve built (and will build) into GitLab CI/CD Security Testing. Note: Gemnasium customers will need Ultimate to take advantage of Security Testing.
A: No, GitLab CI/CD is a Premium functionality and is not a standalone product.
A: GitLab CI/CD for GitHub is a feature of GitLab without stand-alone pricing.
It is part of our Premium (Self-managed & SaaS) Tiers - $19 /user /month (For all GitLab Premium features including CI/CD for GitHub.)
Promotionally, we will make the GitLab CI/CD feature available as part of the Free Tier on GitLab SaaS through 2019-09-22.
A customer only needs 1 service account on GitLab to run pipelines for GitHub code, but will benefit from having more user accounts.
Pro:
Cons:
Developer will have a pass / fail status report in GitHub, but won't be able to drill down to see why a build failed without access to GitLab
Developers won't have access to artifacts, pipelines output traces, registry images, or security reports.
No - It’s not necessary, but enabling developers grants benefits:
Yes - this should be sold against Jenkins / Travis, think about how many users you'd need to access those tools, and that is the user count that should have access to GitLab.
A: GitLab CI/CD for external repos, including GitLab CI/CD for GitHub will be available as part of the Free tier of GitLab SaaS for one-year plus extended six-month (through 2019-09-22). After 2019-09-22 we plan to move the feature to be part of GitLab SaaS Premium tier. Note: this is for GitLab SaaS only - self-managed customers will only have access in Premium & Ultimate.
A: At this time, no. This is the first time we’ve offered a feature like this promotionally in a different tier than it will eventually end up in,.
A: Yes, GitLab CI/CD for GitHub is available on all hosted versions and is available self-managed on GitLab Premium and Ultimate.
A: Self-managed: Premium and Ultimate
GitLab SaaS: Free, Premium and Ultimate (through 2019-09-22)
GitLab SaaS: Premium, Ultimate (after 2019-09-22)
| Stage | Product Category | Works with GitHub? | Notes |
|---|---|---|---|
| Plan | Portfolio management | No | |
| Plan | Issue Tracking | No | |
| Create | Version Control | No | Repos are Mirrored, which is needed for CI/CD, but there’s no mechanism for Merge Conflicts so you can’t actively use the GitLab Repo |
| Create | Code Review | No | |
| Verify | Continuous integration | Yes | |
| Verify | Security Testing | Yes | |
| Package | Container Registry | Yes | On by default once instance container registry enabled |
| Release | CD/Release automation | Yes | E.g. You CAN deploy to GCP using the GKE Integration |
| Configure | Configuration management | Yes | |
| Monitor | Monitoring | Yes |
A: No, GitLab CI/CD for GitHub is being released and launched on the same day. As such, it will not be available for customers to use until after GitLab 10.6 is released on 2018-03-22.
A: We have not made a determination if it will or will not be in the marketplace. It is a
possibility, but requires additional complexity such as augmenting how we price. It is not available today as part of the marketplace.
