GitLab 10.6: CI/CD for GitHub, increased Kubernetes support
Source – jaxenter.com
DevOps without CI/CD is like trying to build a house out of popsicle sticks. Sure, it can be done, but oh man, are you making your life harder than it needs to be. So, the fact that GitLab, one of the most popular Git-repositories on the internet, still didn’t support CI/CD with GitHub has been something of a thing.
Now, that problem is gone forever with GitLab 10.6. GitLab’s popular built-in continuous integration, continuous delivery, and continuous deployment is here and it supports GitHub. This calls for a celebration.
CI/CD support for GitHub
First off, GitLab can work as a one-stop shop for developers. But, as an open source fan, GitLab knows you might want to play with other repositories. And they’re okay with that! GitLab 10.6 has added CI/CD integration with GitHub and other external repos like BitBucket.
Now, GitLab users can create a CI/CD project in GitLab that is connected to an external code repository like GitHub. This will automatically prompt GitLab CI/CD to run whenever code is pushed to GitHub and post CI/CD results back to both repositories whenever completed.
With the GitHub integration, GitLab users can now create a CI/CD project in GitLab connected to an external GitHub.com or GitHub Enterprise code repository. This will automatically prompt GitLab CI/CD to run whenever code is pushed to GitHub and post CI/CD results back to both GitLab and GitHub when completed.
Who will benefit from GitLab 10.6?
GitLab thinks this change will help four specific types of users: open source projects, large enterprises, GitHubbers, and Gemnasium customers.
As part of their prior commitment to supporting open source, GitLab already offers all public projects their highest tier features for free. This means that open source projects on GitHub will be able to handle hundreds of concurrent jobs with 50,000 free pipeline minutes.
Additionally, large enterprises have already been asking for this kind of feature to coordinate between various teams using different tools. Standardization across a number of Git repos is difficult if you don’t have CI/CD support. This release solves a fairly pressing issue for a number of teams.
In general, though, all GitHubbers will definitely benefit from this new change. For the next year, the GitLab CI/CD for GitHub is completely free. Anyone with a GitHub account can access this feature for their personal project, startup idea, or more. This offer comes with 2000 free pipeline minutes per month. But if developers feel like they need a little more horsepower, they can always upgrade their plan to get a little more juice under the hood.
Furthermore, GitLab just recently acquired Gemnasium, a dependency monitoring software company. Gemnasium’s security monitoring system is winding down and the service itself should be shut down by May 15. In the transition period, GitLab wants to make it even easier to help Gemnasium users migrate over. Gemnasium features have already been folded in to the GitLab security scanning. But now, the Gemnasium customers can utilize GitLab CI/CD for their security needs.
Kubernetes support on GitLab
As part of GitLab 10.4, GitLab released Kubernetes Cluster Integration and GKE Integration. Developers could connect existing clusters to their projects or create brand new ones with Google Kubernetes Engine using the new Clusters page in the CI/CD section.
GitLab is committed to making it even easier for users to utilize Kubernetes. Now, users can deploy a GitLab Runner to their connected Kubernetes cluster with a single click. They can also monitor their connected clusters or see the IP address of an Ingress controller from within GitLab.
There are a number of other improvements to GitLab 10.6, including changes to their Static Application Security Testing (SAST), an exceedingly clever branches overview, and even Filipino, Indonesian, and Turkish language support. Head on over to the changelog for a full listing.