When thinking about migrating off of legacy systems, the project can often times seem too large or too daunting to undertake on your own. Our DevOps experts have been in the field for years, and many of them have lead CI/CD transitions at their own organizations before joining GitLab. We leverage this experience as well as experience migrating customers off their legacy Jenkins or Cloudbees systems to ensure a successful transition that improves your time to market and expands the value you realize from your GitLab implementation.
For small teams, simply converting the scripts that are in place to the simple .gitlab-ci.yml syntax is often enough to get started with GitLab CI/CD. In larger enterprises, a project plan and specific engagement approach is required to ensure success.
Our engagement approach for migrating off of Jenkins and into modern CI/CD practices with GitLab CI/CD includes three phases: Evaluation, Education, and Empowerment.
During the Evaluation Phase, our team will work with your experts to understand the current Jenkins environment, what technologies and plugins are in use and what positive business outcomes the team wants to see out of the transition. We'll also identify essential integration points in terms of how and where your software is deployed. During this time, we will also work with key stakeholders throughout your organization to understand who we can identify as mentors or "center of excellence" leaders to help lead the change management required to adopt CI/CD best practices.
As an output to this phase, we will provide a summarized evaluation of the technologies involved, as well as recommendations as to where to start the next two phases of the engagement.
During the education phase, we'll work with your identified leaders and early adopters to teach the best practices and ways that GitLab CI/CD can be a benefit to the team, no matter what the technology stack. We will provide GitLab CI/CD training as well as consulting about how to apply the models available to your organization's environment.
After this phase is complete, you and your early adopter teams will be equipped to be GitLab CI/CD evangelists to the rest of your organization - and help teams that want to be the next to adopt GitLab CI/CD.
In the empowerment phase, we will work with your teams to build templates, best practice guides, and guardrails to aid with the rollout of the migration plan to the rest of the enterprise.
Our number one goal is to empower your engineers, team leaders, and DevOps teams to understand the benefits of transitioning to GitLab CI/CD. This enables you to get the most value possible out of your GitLab installation, and realize the benefits of a DevOps platform delivered as a single application.
Once templates and best practices have been established, the GitLab Professional Services can continue to work side-by-side with your team to direct more teams through their transition. Alternatively, a more hands-off self-service organic approach to adoption is also possible, shortening the overall length of the services engagement. We will work with your team to understand your specific needs and propose a statement of work that matches those.