Blog - Jenkins to GitLab: The ultimate guide to modernizing your CI/CD environment - Nov 2023
<!-- Epic Title Guide: Dates should be using ISO dates, see https://about.gitlab.com/handbook/communication/#writing-style-guidelines Content: Title - Author - Publish Month, Publish Year --> ## Activity Summary 1. Who is our audience? Customers who want to migrate from Jenkins to GitLab, with migration phases, 1. What is the best content type (blog post, video, how-to) to deliver this message? Blog, tutorial. 1. How does this content help our audience? Ideally the content helps to see value in GitLab CI, and plan the migration phases while adopting new projects with GitLab CI already. 1. How does this content help us achieve our goals? Contributes to the CI Adoption Use case WG. ## Team or Individual DRIs <!-- Please add team label to epic --> - Author: @iganbaruch - Reviewers: @dnsmichi @lstahlman ## Relevant Issues, Epics or resources - [DevRel workstreams in the CI use case adoption WG](https://gitlab.com/groups/gitlab-com/marketing/developer-relations/-/epics/317#work-streams) - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/34615 <!-- these labels should be included on all templates --> <!-- Example: Note: These are samples for guidance, please add relevant labels for activity region, type, quarter or any other labels relevant to your team/program. Please include additional relevant labels here. --> <!--Link to parent epic where necessary. Please choose the quarterly epic from the FY24 main epic https://gitlab.com/groups/gitlab-com/marketing/developer-relations/-/epics/98 --> <!-- Link to Child epic where necessary --> /cc @gitlab-de <!-- Mention team members that should be aware of the epic --> /cc
epic