GitLab 5 Minute Clips of GitLab, 23 Sep 2022

Previous Meeting

⏯

youtube image

►

From YouTube: CI/CD Modernization with GitLab

Description

Overview on how to solve various challenges from scalability to onboarding and how GitLab CI/CD can help.

Slide: Solving for scalability

- https://docs.gitlab.com/runner/
- https://docs.gitlab.com/runner/fleet_scaling/
- https://docs.gitlab.com/ee/ci/cloud_deployment/
- https://gitlab.com/gitlab-org/gitlab-environment-toolkit
- https://docs.gitlab.com/ee/user/permissions.html

Slide: Increase visibility

- https://about.gitlab.com/topics/single-application/
- https://docs.gitlab.com/ee/ci/testing/
- https://docs.gitlab.com/ee/ci/pipelines/pipeline_efficiency.html#pipeline-monitoring
- https://about.gitlab.com/solutions/dev-sec-ops/

Slide: Enable standardization

- https://docs.gitlab.com/ee/ci/yaml/index.html#include
- https://docs.gitlab.com/ee/ci/yaml/#extends
- https://docs.gitlab.com/ee/ci/yaml/yaml_optimization.html
- https://docs.gitlab.com/ee/user/project/merge_requests/
- https://docs.gitlab.com/ee/ci/environments/deployment_approvals.html

Slide: Speed up onboarding

- https://about.gitlab.com/handbook/
- https://docs.gitlab.com/ee/user/project/pages/
- https://docs.gitlab.com/ee/integration/gitpod.html
- https://docs.gitlab.com/ee/ci/review_apps/

Slide: App modernization

- https://docs.gitlab.com/ee/user/clusters/agent/gitops.html
- https://docs.gitlab.com/ee/operations/feature_flags.html
- https://docs.gitlab.com/ee/ci/pipelines/downstream_pipelines.html
- https://about.gitlab.com/topics/multicloud/
- https://docs.gitlab.com/ee/ci/cloud_services/

A

Hey y'all welcome to the session on Ci City, modernization with gitlab I'm, Joe Randazzo, a Senior Solutions architect at LM and I'm part of a team who specializes in helping clients, focus on the technical solution, while also understanding the customers, business outcomes that they're trying to achieve I've talked with hundreds of customers over the past couple years and found similar challenges in the ipd space. The common thing is that software teams are trying to respond to business Innovation, but they're sprawling tool chain is holding them back in this video.

A

We explore a range of challenges, including scalability, to onboarding with existing tool chains, and we see how gitlab CI CD can enable your organization that can lead to app modernization.

A

Now before diving in I found an interesting survey result and a recent gitlab devsecop survey found that 70 of those surveyed are aiming to consolidate their sprawling tool chain because of challenges with either monitoring deployment, delays or unhappy. Developers.

A

Now we're this we're made this deployment delay or frustration, be driven from uh here's, how it may look with your organization at a 10, 000 foot View. What has been uncovered is, as you start to grow with the number of projects and tools, the developer productivity hits a plateau.

A

A big reason is due to the sheer number of tool Integrations that have been built over time. This is observed to be that complexity and CID Stacks from the toil of Integrations.

A

Now, let's dig a little deeper into some of these challenges that we see on the field first up scalability. This is one that is common among platform. Teams is showing that the systems they build can help scale out to the next 100 developers or services.

A

Some of these challenges may be maintaining a long list of build agents that have complicated, installs or brittle to the touch. Some cicd options come with plugins that become outdated over time or difficult to maintain or if you're migrating from a monolithic app to microservices, building out skilled pipeline architectures can be really difficult.

A

Now, in terms of visibility, this can be context. Switching between three applications, including your code review, building status or even list of environments, our QA teams, the right letters to get unit and integration testing colloquial developer can also be difficult for even security teams, oftentimes developers and security is siled and don't have visibility where that vulnerability was introduced.

A

Now for the third challenge, standards can be tricky to enforced across hundreds of services that may be due to not having the right components to build out for reasonable pipelines or inconsistent gating between teams into your production, environment and last that could be easily overlooked, is onboarding oftentimes. A new engineer hire may have too many tools to learn in just the first few weeks, along with no single source of Truth and documentation and processes.

A

These challenges start to compound and turns into this mountain climb efforts slowing down your team so up next, let's take a look at how gitlab can help develop some of these challenges.

A

Now, when it comes to solving for scalability within gitlab cicd, the git lab Runner is your starting point for automating your processes. It's a lightweight agent, written goat. That is easy to maintain and scale. The runner has the ability to Auto scale quickly to provisioning job in the nth degree, where we even seeing organizations with 30 000 developers pushed simultaneously if you're an organization that adopted the cloud. There are a wide range of cloud native star templates to help you build and push to your services.

A

There's also infrastructures. Code quick starts to help. You launch gitlab within your cloud provider, to easily maintain your environment going forward with performance and scale in mind, and, lastly, gitlab is a single devops platform that provides a single permission model between development through deployment. This helps your team minimize on pitching together, Integrations and access to services for your team.

A

How does gitlab style for visibility as gitlab is a single platform and a single pane, The Experience between code reviews through automating, your citd pipelines, 15 lists your engineer will be able to see what was committed and how it's available from the one single view. Without jumping between different applications, even your QA teams can incorporate unit and integration tapping within the pipeline to provide faster feedback and identify quality degradation before production teams will also have application security testing built into the pipeline to prevent vulnerabilities from getting into production.

A

And, lastly, as gitlab is a single pane, it encourages devops teams to be a team sport in your organization.

A

Now we often hear in the field that a new team is onboarding and starts to build out a test and deployment pipeline.

A

Then they come to find that as already done 18 months ago, as you can imagine, if you start to onboard new teams with Engineers or ramping up new services within the next year, this won't scale well with gitlab. Cicd teams can Define Center of Excellence by using pipeline catalog that allow you various teams to consume a template and ensure consistency.

A

Similarly, you can build out reusable workflows with overriding configuration management- that's built in now. This allows your team to build out dry principles or don't repeat yourself, to standardize the build testing and deployment steps. And, lastly, because code review and cipd are paired together, you can Define Rich change controls during environment promotion.

A

On one topic that can easily Miss is how the developer onboarding experience is. Most organizations aim to make it a memorable and exciting experience for team members to join in just the first few weeks. It will have any single devops platform spanning from idea source code management cicd to security and, as a result, this immediately allows your team to learn one tool versus four or five tools.

A

Now also with a combination of the git repository gitlab static Pages, you can Define your single source of Truth for application, documentation and processes if you're curious and how they've looked in the real world take a look at the gitlab handbook which serves over 1800 employees who are all completely remote.

A

And lastly, maybe a new developer may ask how can I spin up a quick development environment to the service or application that I begin to develop new team members can also do this with review apps or get pod integration.

A

Now, another initiative we see with customers, that's migrating their legacy, monolithic, apps and modernizing how they are in the cloud. Gitlab can support this initiative in a number of ways, one if your team is deploying to kubernetes, there is a git lab agent for kubernetes solution that can manage GitHub workflows for advanced deployments.

A

Progressive delivery has been a common topic as well, and the question is: how can I State many point Futures to my users and quickly roll back feature? Flags can serve your application and all be managed within the Atlanta. Another topic with customers is managing microservice pipelines and project dependencies pipeline orchestration can be handled here across multiple projects to simplify those Downstream deployments.

A

And lastly, if your organization is considering multi-cloud architecture, you'll have cicd is agnostic and plays well with various Cloud providers enabling portability between services.

A

Now, to recap: what we discussed instead of that mountain climb effort with your existing tool chain, simplifying your tool chain into a single devops platform, allows your team to focus on customer delivery and not cool chains and ultimately leading to a successful modernization of your applications.

A

If you're interested in discussing gitlab tea, I could do with a solution. Architect, please reach out to our Dell team for a deep dive thanks for your time and have a good day.