[{"data":1,"prerenderedAt":820},["ShallowReactive",2],{"/en-us/blog/16-ways-to-get-the-most-out-of-software-documentation":3,"navigation-en-us":40,"banner-en-us":451,"footer-en-us":461,"blog-post-authors-en-us-Sharon Gaudin":702,"blog-related-posts-en-us-16-ways-to-get-the-most-out-of-software-documentation":716,"blog-promotions-en-us":758,"next-steps-en-us":810},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":20,"description":17,"extension":25,"externalUrl":26,"featured":14,"heroImage":19,"isFeatured":14,"meta":27,"navigation":28,"path":29,"publishedDate":20,"rawbody":30,"seo":31,"slug":13,"stem":35,"tagSlugs":36,"tags":38,"template":15,"updatedDate":26,"__hash__":39},"blogPosts/en-us/blog/16-ways-to-get-the-most-out-of-software-documentation.yml","How to get the most out of software documentation",[7],"sharon-gaudin",[9],"Sharon Gaudin","\n\nIt’s not a glamorous part of a DevOps platform, but software documentation is easy, sometimes hands-free, and, if done correctly, can help speed up development and deployment. Here are some tips to refresh your software documentation practice.\n\n## Defining documentation\n\nSoftware documentation – which includes everything from manuals to system and design requirements, change lists, code comments, and alert records – is a way to unify efforts between projects and DevOps teams, and to share specialized knowledge and guidance. It’s also a way to standardize practices and benchmark metrics. There’s a direct correlation between creating clear, comprehensive, searchable, up-to-date, and well-organized documents and a DevOps team’s success.\n\nNeed proof? According to the [Accelerate State of DevOps 2021 report](https://gitlab.com/gitlab-com/www-gitlab-com/uploads/069ee8e2ee6af463cf0aafcd89eda33e/state-of-devops-2021.pdf) from DORA, the DevOps Research and Assessment team at Google, DevOps teams with solid documentation practices are 2.4 times more likely to meet or exceed their reliability targets, 3.8 times more likely to implement security practices, and 2.5 times more likely to fully leverage the cloud.\n\nMaking sure you have strong documentation actually is one of the six suggestions the DORA report gave DevOps professionals who [want to become elite team performers](/blog/how-to-make-your-devops-team-elite-performers/).\n\nAs you work on a [DevOps platform](/solutions/devops-platform/) and create new efficiencies and processes, you will want to document them so you can carry them forward. No continually reinventing the wheel for you.\n\n### Tips for creating solid software documentation\n\nSo how do you go about building good documentation? Here are some basic steps to follow:\n\n- You need to decide who is responsible for the documentation. What works best for your team and your organization? Does the project need a [technical writer](https://handbook.gitlab.com/handbook/product/ux/technical-writing/) or can one of your developers handle it? Give one person or just a few people ownership of documentation. You’re more likely to have quality software documentation when someone has clear responsibility and no one can pass the buck.\n\n- Don’t forget about incorporating user experience into your documentation. It will give you a different view on use cases and experiences and enable readers to have their success moment [more quickly](https://docs.gitlab.com/ci/quick_start/).\n- Think about the security requirements for your software. For instance, when a project uses network communication over public transport, does it provide secure communication with TLS and/or https? Inform users about [support policies for security releases](https://docs.gitlab.com/policy/maintenance/), allowing to plan accordingly for upgrades and maintenance windows. Additionally, what measurements do you need to take to make sure it complies with company security policies? Note that information in your documentation.\n\n- Use your documentation to explain technical decisions and share insights into [reference architectures](https://docs.gitlab.com/administration/reference_architec/ tures/). When debugging a problem, it is helpful to learn about the decisions, and also have ‘get help’ and [‘troubleshooting’ sections](https://docs.gitlab.com/ci/troubleshooting/) in your documentation.\n\n- Provide details about issues you faced with the project and how you worked them out. Make sure the details are explained so that others can easily understand them. Add URLs to issues or epics into your documentation to allow readers to follow, for example the [version history for product features](https://docs.gitlab.com/development/documentation/styleguide/#version-text-in-the-version-history) in the GitLab documentation.\n\n- There should be specific rules about how to change, expand and update documentation. Create [documentation style guides](https://docs.gitlab.com/development/documentation/styleguide/), including requirements, examples, use cases and specifications for writing for a global audience. If changes are made creating inconsistent data formats, it can be more difficult to organize and search documents.\n\n- Don’t just document at the end of a project. It should be done continuously throughout the development and deployment lifecycle – from planning through monitoring and feedback. (We’ll give you more tips about this below.)\n\n- Give people who are responsible for documentation the [training](https://university.gitlab.com/courses/gitlab-technical-writing-fundamentals) they need in how to collect data, write, organize, and maintain it.\n\n- Make sure the [people responsible for documentation](https://handbook.gitlab.com/handbook/product/ux/technical-writing/#designated-technical-writers) are included in all aspects of the DevOps lifecycle. Bring them into planning, design, and testing meetings. They can’t write about or collect information about what they don’t know is happening.\n\n- Make use of data created by automated processes. (Again, there’s more information on this below.)\n\n- Make sure your documentation isn’t just paraphrasing what the source code flow does. Explain the “why” as well as the use case for the project. Dependending on the size and users, your audiences may differ, and the introduction needs an [overview with different navigation routes](https://docs.gitlab.com/).\n\n- There’s no one right way to handle documentation. What you need for documentation may vary depending on things like the size and nature of your organization, the scope of your software projects, and compliance issues. A hospital or financial institution’s documentation needs might differ from those of a small, private company.\n\n## Continuous software documentation\n\nMuch like there are continuous integration and deployment, there also can be continuous documentation. You can make the automated processes on a DevOps platform do a good chunk of your documentation work by having them capture key information throughout the DevOps lifecycle and funnel it into your documentation stores. Make it part of your development workflow by approaching documentation with a DevOps mindset. Software documentation is easier and more helpful when it’s done continuously.\n\nYou can leverage existing tools to generate, convert and present documentation. GitLab provides an extensive REST API, which allows to [update the wiki](https://docs.gitlab.com/api/wikis/) programmantically, or modify a Markdown file in the Git repository from your CI/CD pipelines. If you want to present the documentation on a website, you can use [MkDocs](https://www.mkdocs.org/) to generate a static documentation website [served with GitLab Pages](https://gitlab.com/pages/mkdocs) for example. Code documentation with [Doxygen](https://www.doxygen.nl/manual/docblocks.html) can be generated in the same way as a [website reference documentation](https://gitlab.com/pages/doxygen).\n### Tips to make documentation easier and more continuous\n\n- The DevOps platform’s automated systems, which govern processes and monitor everything from system to software configurations, generate logs that can create a real-time, ongoing stream of documentation.\n\n- Scripts and configuration files that control automated processes, like testing, hold important configuration data that can be fed into documentation.\n\n- Issue and alert logs, which generally contain information about problems, can be automatically documented.\n- Integrated [Observability](https://docs.gitlab.com/operations/) keeps track of performance and availability of the software and also can add to documentation by providing access to metrics, traces and log dashboards and panels. \nThese are just a few ways to automatically feed your continuous documentation operation. Sure, there are forms of documentation that will need some hands-on, but there are a lot that can be generated as part of the ongoing process. The data is there, so make good use of it.\n\n“Good documentation is foundational for successfully implementing DevOps capabilities,” the DORA report noted. “Teams with high quality documentation are better able to implement technical practices and perform better as a whole… From security to testing, documentation is a key way to share specialized knowledge and guidance both between these specialized sub-teams and with the wider team.”\n\n_[Michael Friedrich](/company/team/#dnsmichi), Senior Developer Evangelist, contributed to this blog post._\n","devsecops",{"slug":13,"featured":14,"template":15},"16-ways-to-get-the-most-out-of-software-documentation",false,"BlogPost",{"title":5,"description":17,"authors":18,"heroImage":19,"date":20,"body":10,"category":11,"tags":21},"Want to get even more mileage out of your DevOps platform? Better software documentation is the answer. Here are tips to help you get started.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668339/Blog/Hero%20Images/a-tale-of-two-editors.jpg","2022-01-11",[22,23,24],"DevOps platform","workflow","collaboration","yml",null,{},true,"/en-us/blog/16-ways-to-get-the-most-out-of-software-documentation","seo:\n  title: How to get the most out of software documentation\n  description: >-\n    Want to get even more mileage out of your DevOps platform? Better software\n    documentation is the answer. Here are tips to help you get started.\n  ogTitle: How to get the most out of software documentation\n  ogDescription: >-\n    Want to get even more mileage out of your DevOps platform? Better software\n    documentation is the answer. Here are tips to help you get started.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668339/Blog/Hero%20Images/a-tale-of-two-editors.jpg\n  ogUrl: >-\n    https://about.gitlab.com/blog/16-ways-to-get-the-most-out-of-software-documentation\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: >-\n    https://about.gitlab.com/blog/16-ways-to-get-the-most-out-of-software-documentation\ncontent:\n  title: How to get the most out of software documentation\n  description: >-\n    Want to get even more mileage out of your DevOps platform? Better software\n    documentation is the answer. Here are tips to help you get started.\n  authors:\n    - Sharon Gaudin\n  heroImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749668339/Blog/Hero%20Images/a-tale-of-two-editors.jpg\n  date: '2022-01-11'\n  body: \"\n\n\n    It’s not a glamorous part of a DevOps platform, but software documentation\n    is easy, sometimes hands-free, and, if done correctly, can help speed up\n    development and deployment. Here are some tips to refresh your software\n    documentation practice.\n\n\n    ## Defining documentation\n\n\n    Software documentation – which includes everything from manuals to system\n    and design requirements, change lists, code comments, and alert records – is\n    a way to unify efforts between projects and DevOps teams, and to share\n    specialized knowledge and guidance. It’s also a way to standardize practices\n    and benchmark metrics. There’s a direct correlation between creating clear,\n    comprehensive, searchable, up-to-date, and well-organized documents and a\n    DevOps team’s success.\n\n\n    Need proof? According to the [Accelerate State of DevOps 2021\n    report](https://gitlab.com/gitlab-com/www-gitlab-com/uploads/069ee8e2ee6af4\\\n    63cf0aafcd89eda33e/state-of-devops-2021.pdf) from DORA, the DevOps Research\n    and Assessment team at Google, DevOps teams with solid documentation\n    practices are 2.4 times more likely to meet or exceed their reliability\n    targets, 3.8 times more likely to implement security practices, and 2.5\n    times more likely to fully leverage the cloud.\n\n\n    Making sure you have strong documentation actually is one of the six\n    suggestions the DORA report gave DevOps professionals who [want to become\n    elite team\n    performers](/blog/how-to-make-your-devops-team-elite-performers/).\n\n\n    As you work on a [DevOps platform](/solutions/devops-platform/) and create\n    new efficiencies and processes, you will want to document them so you can\n    carry them forward. No continually reinventing the wheel for you.\n\n\n    ### Tips for creating solid software documentation\n\n\n    So how do you go about building good documentation? Here are some basic\n    steps to follow:\n\n\n    - You need to decide who is responsible for the documentation. What works\n    best for your team and your organization? Does the project need a [technical\n    writer](https://handbook.gitlab.com/handbook/product/ux/technical-writing/)\n    or can one of your developers handle it? Give one person or just a few\n    people ownership of documentation. You’re more likely to have quality\n    software documentation when someone has clear responsibility and no one can\n    pass the buck.\n\n\n    - Don’t forget about incorporating user experience into your documentation.\n    It will give you a different view on use cases and experiences and enable\n    readers to have their success moment [more\n    quickly](https://docs.gitlab.com/ci/quick_start/).\\\n\n\n    - Think about the security requirements for your software. For instance,\n    when a project uses network communication over public transport, does it\n    provide secure communication with TLS and/or https? Inform users about\n    [support policies for security\n    releases](https://docs.gitlab.com/policy/maintenance/), allowing to\n    plan accordingly for upgrades and maintenance windows. Additionally, what\n    measurements do you need to take to make sure it complies with company\n    security policies? Note that information in your documentation.\n\n\n    - Use your documentation to explain technical decisions and share insights\n    into [reference\n    architectures](https://docs.gitlab.com/administration/reference_architec/\n    tures/). When debugging a problem, it is helpful to learn about the\n    decisions, and also have ‘get help’ and [‘troubleshooting’\n    sections](https://docs.gitlab.com/ci/troubleshooting/) in your\n    documentation.\n\n\n    - Provide details about issues you faced with the project and how you worked\n    them out. Make sure the details are explained so that others can easily\n    understand them. Add URLs to issues or epics into your documentation to\n    allow readers to follow, for example the [version history for product\n    features](https://docs.gitlab.com/development/documentation/styleguide/#\\\n    version-text-in-the-version-history) in the GitLab documentation.\n\n\n    - There should be specific rules about how to change, expand and update\n    documentation. Create [documentation style\n    guides](https://docs.gitlab.com/development/documentation/styleguide/),\n    including requirements, examples, use cases and specifications for writing\n    for a global audience. If changes are made creating inconsistent data\n    formats, it can be more difficult to organize and search documents.\n\n\n    - Don’t just document at the end of a project. It should be done\n    continuously throughout the development and deployment lifecycle – from\n    planning through monitoring and feedback. (We’ll give you more tips about\n    this below.)\n\n\n    - Give people who are responsible for documentation the\n    [training](https://university.gitlab.com/courses/gitlab-technical-writing-f\\\n    undamentals) they need in how to collect data, write, organize, and maintain\n    it.\n\n\n    - Make sure the [people responsible for\n    documentation](https://handbook.gitlab.com/handbook/product/ux/technical-wr\\\n    iting/#designated-technical-writers) are included in all aspects of the\n    DevOps lifecycle. Bring them into planning, design, and testing meetings.\n    They can’t write about or collect information about what they don’t know is\n    happening.\n\n\n    - Make use of data created by automated processes. (Again, there’s more\n    information on this below.)\n\n\n    - Make sure your documentation isn’t just paraphrasing what the source code\n    flow does. Explain the “why” as well as the use case for the\n    project. Dependending on the size and users, your audiences may differ, and\n    the introduction needs an [overview with different navigation\n    routes](https://docs.gitlab.com/).\n\n\n    - There’s no one right way to handle documentation. What you need for\n    documentation may vary depending on things like the size and nature of your\n    organization, the scope of your software projects, and compliance issues. A\n    hospital or financial institution’s documentation needs might differ from\n    those of a small, private company.\n\n\n    ## Continuous software documentation\n\n\n    Much like there are continuous integration and deployment, there also can be\n    continuous documentation. You can make the automated processes on a DevOps\n    platform do a good chunk of your documentation work by having them capture\n    key information throughout the DevOps lifecycle and funnel it into your\n    documentation stores. Make it part of your development workflow by\n    approaching documentation with a DevOps mindset. Software documentation is\n    easier and more helpful when it’s done continuously.\n\n\n    You can leverage existing tools to generate, convert and present\n    documentation. GitLab provides an extensive REST API, which allows to\n    [update the wiki](https://docs.gitlab.com/api/wikis/)\n    programmantically, or modify a Markdown file in the Git repository from your\n    CI/CD pipelines. If you want to present the documentation on a website, you\n    can use [MkDocs](https://www.mkdocs.org/) to generate a static documentation\n    website [served with GitLab Pages](https://gitlab.com/pages/mkdocs) for\n    example. Code documentation with\n    [Doxygen](https://www.doxygen.nl/manual/docblocks.html) can be generated in\n    the same way as a [website reference\n    documentation](https://gitlab.com/pages/doxygen).\\\n\n\n    ### Tips to make documentation easier and more continuous\n\n\n    - The DevOps platform’s automated systems, which govern processes and\n    monitor everything from system to software configurations, generate logs\n    that can create a real-time, ongoing stream of documentation.\n\n\n    - Scripts and configuration files that control automated processes, like\n    testing, hold important configuration data that can be fed into\n    documentation.\n\n\n    - Issue and alert logs, which generally contain information about problems,\n    can be automatically documented.\\\n\n\n    - Integrated [Observability](https://docs.gitlab.com/operations/) keeps track of\n    performance and availability of the software and also can add to\n    documentation by providing access to metrics, traces and log dashboards and\n    panels. \\\n\n\n    These are just a few ways to automatically feed your continuous\n    documentation operation. Sure, there are forms of documentation that will\n    need some hands-on, but there are a lot that can be generated as part of the\n    ongoing process. The data is there, so make good use of it.\n\n\n    “Good documentation is foundational for successfully implementing DevOps\n    capabilities,” the DORA report noted. “Teams with high quality documentation\n    are better able to implement technical practices and perform better as a\n    whole… From security to testing, documentation is a key way to share\n    specialized knowledge and guidance both between these specialized sub-teams\n    and with the wider team.”\n\n\n    _[Michael Friedrich](/company/team/#dnsmichi), Senior Developer Evangelist,\n    contributed to this blog post._\\n\"\n  category: devsecops\n  tags:\n    - DevOps platform\n    - workflow\n    - collaboration\nconfig:\n  slug: 16-ways-to-get-the-most-out-of-software-documentation\n  featured: false\n  template: BlogPost\n",{"title":5,"description":17,"ogTitle":5,"ogDescription":17,"noIndex":14,"ogImage":19,"ogUrl":32,"ogSiteName":33,"ogType":34,"canonicalUrls":32},"https://about.gitlab.com/blog/16-ways-to-get-the-most-out-of-software-documentation","https://about.gitlab.com","article","en-us/blog/16-ways-to-get-the-most-out-of-software-documentation",[37,23,24],"devops-platform",[22,23,24],"1qMUuA4bHB88SpZmSx7s3AN4bYRzqx8HGs-g5fbIJ9Q",{"data":41},{"logo":42,"freeTrial":47,"sales":52,"login":57,"items":62,"search":371,"minimal":402,"duo":421,"switchNav":430,"pricingDeployment":441},{"config":43},{"href":44,"dataGaName":45,"dataGaLocation":46},"/","gitlab logo","header",{"text":48,"config":49},"Get free trial",{"href":50,"dataGaName":51,"dataGaLocation":46},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":53,"config":54},"Talk to sales",{"href":55,"dataGaName":56,"dataGaLocation":46},"/sales/","sales",{"text":58,"config":59},"Sign in",{"href":60,"dataGaName":61,"dataGaLocation":46},"https://gitlab.com/users/sign_in/","sign in",[63,90,185,190,292,352],{"text":64,"config":65,"cards":67},"Platform",{"dataNavLevelOne":66},"platform",[68,74,82],{"title":64,"description":69,"link":70},"The intelligent orchestration platform for DevSecOps",{"text":71,"config":72},"Explore our Platform",{"href":73,"dataGaName":66,"dataGaLocation":46},"/platform/",{"title":75,"description":76,"link":77},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":78,"config":79},"Meet GitLab Duo",{"href":80,"dataGaName":81,"dataGaLocation":46},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":83,"description":84,"link":85},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":86,"config":87},"Learn more",{"href":88,"dataGaName":89,"dataGaLocation":46},"/why-gitlab/","why gitlab",{"text":91,"left":28,"config":92,"link":94,"lists":98,"footer":167},"Product",{"dataNavLevelOne":93},"solutions",{"text":95,"config":96},"View all Solutions",{"href":97,"dataGaName":93,"dataGaLocation":46},"/solutions/",[99,123,146],{"title":100,"description":101,"link":102,"items":107},"Automation","CI/CD and automation to accelerate deployment",{"config":103},{"icon":104,"href":105,"dataGaName":106,"dataGaLocation":46},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[108,112,115,119],{"text":109,"config":110},"CI/CD",{"href":111,"dataGaLocation":46,"dataGaName":109},"/solutions/continuous-integration/",{"text":75,"config":113},{"href":80,"dataGaLocation":46,"dataGaName":114},"gitlab duo agent platform - product menu",{"text":116,"config":117},"Source Code Management",{"href":118,"dataGaLocation":46,"dataGaName":116},"/solutions/source-code-management/",{"text":120,"config":121},"Automated Software Delivery",{"href":105,"dataGaLocation":46,"dataGaName":122},"Automated software delivery",{"title":124,"description":125,"link":126,"items":131},"Security","Deliver code faster without compromising security",{"config":127},{"href":128,"dataGaName":129,"dataGaLocation":46,"icon":130},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[132,136,141],{"text":133,"config":134},"Application Security Testing",{"href":128,"dataGaName":135,"dataGaLocation":46},"Application security testing",{"text":137,"config":138},"Software Supply Chain Security",{"href":139,"dataGaLocation":46,"dataGaName":140},"/solutions/supply-chain/","Software supply chain security",{"text":142,"config":143},"Software Compliance",{"href":144,"dataGaName":145,"dataGaLocation":46},"/solutions/software-compliance/","software compliance",{"title":147,"link":148,"items":153},"Measurement",{"config":149},{"icon":150,"href":151,"dataGaName":152,"dataGaLocation":46},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[154,158,162],{"text":155,"config":156},"Visibility & Measurement",{"href":151,"dataGaLocation":46,"dataGaName":157},"Visibility and Measurement",{"text":159,"config":160},"Value Stream Management",{"href":161,"dataGaLocation":46,"dataGaName":159},"/solutions/value-stream-management/",{"text":163,"config":164},"Analytics & Insights",{"href":165,"dataGaLocation":46,"dataGaName":166},"/solutions/analytics-and-insights/","Analytics and insights",{"title":168,"items":169},"GitLab for",[170,175,180],{"text":171,"config":172},"Enterprise",{"href":173,"dataGaLocation":46,"dataGaName":174},"/enterprise/","enterprise",{"text":176,"config":177},"Small Business",{"href":178,"dataGaLocation":46,"dataGaName":179},"/small-business/","small business",{"text":181,"config":182},"Public Sector",{"href":183,"dataGaLocation":46,"dataGaName":184},"/solutions/public-sector/","public sector",{"text":186,"config":187},"Pricing",{"href":188,"dataGaName":189,"dataGaLocation":46,"dataNavLevelOne":189},"/pricing/","pricing",{"text":191,"config":192,"link":194,"lists":198,"feature":283},"Resources",{"dataNavLevelOne":193},"resources",{"text":195,"config":196},"View all resources",{"href":197,"dataGaName":193,"dataGaLocation":46},"/resources/",[199,232,255],{"title":200,"items":201},"Getting started",[202,207,212,217,222,227],{"text":203,"config":204},"Install",{"href":205,"dataGaName":206,"dataGaLocation":46},"/install/","install",{"text":208,"config":209},"Quick start guides",{"href":210,"dataGaName":211,"dataGaLocation":46},"/get-started/","quick setup checklists",{"text":213,"config":214},"Learn",{"href":215,"dataGaLocation":46,"dataGaName":216},"https://university.gitlab.com/","learn",{"text":218,"config":219},"Product documentation",{"href":220,"dataGaName":221,"dataGaLocation":46},"https://docs.gitlab.com/","product documentation",{"text":223,"config":224},"Best practice videos",{"href":225,"dataGaName":226,"dataGaLocation":46},"/getting-started-videos/","best practice videos",{"text":228,"config":229},"Integrations",{"href":230,"dataGaName":231,"dataGaLocation":46},"/integrations/","integrations",{"title":233,"items":234},"Discover",[235,240,245,250],{"text":236,"config":237},"Customer success stories",{"href":238,"dataGaName":239,"dataGaLocation":46},"/customers/","customer success stories",{"text":241,"config":242},"Blog",{"href":243,"dataGaName":244,"dataGaLocation":46},"/blog/","blog",{"text":246,"config":247},"The Source",{"href":248,"dataGaName":249,"dataGaLocation":46},"/the-source/","the source",{"text":251,"config":252},"Remote",{"href":253,"dataGaName":254,"dataGaLocation":46},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":256,"items":257},"Connect",[258,263,268,273,278],{"text":259,"config":260},"GitLab Services",{"href":261,"dataGaName":262,"dataGaLocation":46},"/services/","services",{"text":264,"config":265},"Community",{"href":266,"dataGaName":267,"dataGaLocation":46},"/community/","community",{"text":269,"config":270},"Forum",{"href":271,"dataGaName":272,"dataGaLocation":46},"https://forum.gitlab.com/","forum",{"text":274,"config":275},"Events",{"href":276,"dataGaName":277,"dataGaLocation":46},"/events/","events",{"text":279,"config":280},"Partners",{"href":281,"dataGaName":282,"dataGaLocation":46},"/partners/","partners",{"textColor":284,"title":285,"text":286,"link":287},"#000","What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":288,"config":289},"Read the latest",{"href":290,"dataGaName":291,"dataGaLocation":46},"/releases/whats-new/","whats new",{"text":293,"config":294,"lists":296},"Company",{"dataNavLevelOne":295},"company",[297],{"items":298},[299,304,310,312,317,322,327,332,337,342,347],{"text":300,"config":301},"About",{"href":302,"dataGaName":303,"dataGaLocation":46},"/company/","about",{"text":305,"config":306,"footerGa":309},"Jobs",{"href":307,"dataGaName":308,"dataGaLocation":46},"/jobs/","jobs",{"dataGaName":308},{"text":274,"config":311},{"href":276,"dataGaName":277,"dataGaLocation":46},{"text":313,"config":314},"Leadership",{"href":315,"dataGaName":316,"dataGaLocation":46},"/company/team/e-group/","leadership",{"text":318,"config":319},"Team",{"href":320,"dataGaName":321,"dataGaLocation":46},"/company/team/","team",{"text":323,"config":324},"Handbook",{"href":325,"dataGaName":326,"dataGaLocation":46},"https://handbook.gitlab.com/","handbook",{"text":328,"config":329},"Investor relations",{"href":330,"dataGaName":331,"dataGaLocation":46},"https://ir.gitlab.com/","investor relations",{"text":333,"config":334},"Trust Center",{"href":335,"dataGaName":336,"dataGaLocation":46},"/security/","trust center",{"text":338,"config":339},"AI Transparency Center",{"href":340,"dataGaName":341,"dataGaLocation":46},"/ai-transparency-center/","ai transparency center",{"text":343,"config":344},"Newsletter",{"href":345,"dataGaName":346,"dataGaLocation":46},"/company/contact/#contact-forms","newsletter",{"text":348,"config":349},"Press",{"href":350,"dataGaName":351,"dataGaLocation":46},"/press/","press",{"text":353,"config":354,"lists":355},"Contact us",{"dataNavLevelOne":295},[356],{"items":357},[358,361,366],{"text":53,"config":359},{"href":55,"dataGaName":360,"dataGaLocation":46},"talk to sales",{"text":362,"config":363},"Support portal",{"href":364,"dataGaName":365,"dataGaLocation":46},"https://support.gitlab.com","support portal",{"text":367,"config":368},"Customer portal",{"href":369,"dataGaName":370,"dataGaLocation":46},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":372,"login":373,"suggestions":380},"Close",{"text":374,"link":375},"To search repositories and projects, login to",{"text":376,"config":377},"gitlab.com",{"href":60,"dataGaName":378,"dataGaLocation":379},"search login","search",{"text":381,"default":382},"Suggestions",[383,385,389,391,395,399],{"text":75,"config":384},{"href":80,"dataGaName":75,"dataGaLocation":379},{"text":386,"config":387},"Code Suggestions (AI)",{"href":388,"dataGaName":386,"dataGaLocation":379},"/solutions/code-suggestions/",{"text":109,"config":390},{"href":111,"dataGaName":109,"dataGaLocation":379},{"text":392,"config":393},"GitLab on AWS",{"href":394,"dataGaName":392,"dataGaLocation":379},"/partners/technology-partners/aws/",{"text":396,"config":397},"GitLab on Google Cloud",{"href":398,"dataGaName":396,"dataGaLocation":379},"/partners/technology-partners/google-cloud-platform/",{"text":400,"config":401},"Why GitLab?",{"href":88,"dataGaName":400,"dataGaLocation":379},{"freeTrial":403,"mobileIcon":408,"desktopIcon":413,"secondaryButton":416},{"text":404,"config":405},"Start free trial",{"href":406,"dataGaName":51,"dataGaLocation":407},"https://gitlab.com/-/trials/new/","nav",{"altText":409,"config":410},"Gitlab Icon",{"src":411,"dataGaName":412,"dataGaLocation":407},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":409,"config":414},{"src":415,"dataGaName":412,"dataGaLocation":407},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":417,"config":418},"Get Started",{"href":419,"dataGaName":420,"dataGaLocation":407},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":422,"mobileIcon":426,"desktopIcon":428},{"text":423,"config":424},"Learn more about GitLab Duo",{"href":80,"dataGaName":425,"dataGaLocation":407},"gitlab duo",{"altText":409,"config":427},{"src":411,"dataGaName":412,"dataGaLocation":407},{"altText":409,"config":429},{"src":415,"dataGaName":412,"dataGaLocation":407},{"button":431,"mobileIcon":436,"desktopIcon":438},{"text":432,"config":433},"/switch",{"href":434,"dataGaName":435,"dataGaLocation":407},"#contact","switch",{"altText":409,"config":437},{"src":411,"dataGaName":412,"dataGaLocation":407},{"altText":409,"config":439},{"src":440,"dataGaName":412,"dataGaLocation":407},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":442,"mobileIcon":447,"desktopIcon":449},{"text":443,"config":444},"Back to pricing",{"href":188,"dataGaName":445,"dataGaLocation":407,"icon":446},"back to pricing","GoBack",{"altText":409,"config":448},{"src":411,"dataGaName":412,"dataGaLocation":407},{"altText":409,"config":450},{"src":415,"dataGaName":412,"dataGaLocation":407},{"title":452,"button":453,"config":458},"See how agentic AI transforms software delivery",{"text":454,"config":455},"Watch GitLab Transcend now",{"href":456,"dataGaName":457,"dataGaLocation":46},"/events/transcend/virtual/","transcend event",{"layout":459,"icon":460,"disabled":28},"release","AiStar",{"data":462},{"text":463,"source":464,"edit":470,"contribute":475,"config":480,"items":485,"minimal":691},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":465,"config":466},"View page source",{"href":467,"dataGaName":468,"dataGaLocation":469},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":471,"config":472},"Edit this page",{"href":473,"dataGaName":474,"dataGaLocation":469},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":476,"config":477},"Please contribute",{"href":478,"dataGaName":479,"dataGaLocation":469},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":481,"facebook":482,"youtube":483,"linkedin":484},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[486,533,586,630,657],{"title":186,"links":487,"subMenu":502},[488,492,497],{"text":489,"config":490},"View plans",{"href":188,"dataGaName":491,"dataGaLocation":469},"view plans",{"text":493,"config":494},"Why Premium?",{"href":495,"dataGaName":496,"dataGaLocation":469},"/pricing/premium/","why premium",{"text":498,"config":499},"Why Ultimate?",{"href":500,"dataGaName":501,"dataGaLocation":469},"/pricing/ultimate/","why ultimate",[503],{"title":504,"links":505},"Contact Us",[506,509,511,513,518,523,528],{"text":507,"config":508},"Contact sales",{"href":55,"dataGaName":56,"dataGaLocation":469},{"text":362,"config":510},{"href":364,"dataGaName":365,"dataGaLocation":469},{"text":367,"config":512},{"href":369,"dataGaName":370,"dataGaLocation":469},{"text":514,"config":515},"Status",{"href":516,"dataGaName":517,"dataGaLocation":469},"https://status.gitlab.com/","status",{"text":519,"config":520},"Terms of use",{"href":521,"dataGaName":522,"dataGaLocation":469},"/terms/","terms of use",{"text":524,"config":525},"Privacy statement",{"href":526,"dataGaName":527,"dataGaLocation":469},"/privacy/","privacy statement",{"text":529,"config":530},"Cookie preferences",{"dataGaName":531,"dataGaLocation":469,"id":532,"isOneTrustButton":28},"cookie preferences","ot-sdk-btn",{"title":91,"links":534,"subMenu":543},[535,539],{"text":536,"config":537},"DevSecOps platform",{"href":73,"dataGaName":538,"dataGaLocation":469},"devsecops platform",{"text":540,"config":541},"AI-Assisted Development",{"href":80,"dataGaName":542,"dataGaLocation":469},"ai-assisted development",[544],{"title":545,"links":546},"Topics",[547,552,557,562,567,571,576,581],{"text":548,"config":549},"CICD",{"href":550,"dataGaName":551,"dataGaLocation":469},"/topics/ci-cd/","cicd",{"text":553,"config":554},"GitOps",{"href":555,"dataGaName":556,"dataGaLocation":469},"/topics/gitops/","gitops",{"text":558,"config":559},"DevOps",{"href":560,"dataGaName":561,"dataGaLocation":469},"/topics/devops/","devops",{"text":563,"config":564},"Version Control",{"href":565,"dataGaName":566,"dataGaLocation":469},"/topics/version-control/","version control",{"text":568,"config":569},"DevSecOps",{"href":570,"dataGaName":11,"dataGaLocation":469},"/topics/devsecops/",{"text":572,"config":573},"Cloud Native",{"href":574,"dataGaName":575,"dataGaLocation":469},"/topics/cloud-native/","cloud native",{"text":577,"config":578},"AI for Coding",{"href":579,"dataGaName":580,"dataGaLocation":469},"/topics/devops/ai-for-coding/","ai for coding",{"text":582,"config":583},"Agentic AI",{"href":584,"dataGaName":585,"dataGaLocation":469},"/topics/agentic-ai/","agentic ai",{"title":587,"links":588},"Solutions",[589,591,593,598,602,605,609,612,614,617,620,625],{"text":133,"config":590},{"href":128,"dataGaName":133,"dataGaLocation":469},{"text":122,"config":592},{"href":105,"dataGaName":106,"dataGaLocation":469},{"text":594,"config":595},"Agile development",{"href":596,"dataGaName":597,"dataGaLocation":469},"/solutions/agile-delivery/","agile delivery",{"text":599,"config":600},"SCM",{"href":118,"dataGaName":601,"dataGaLocation":469},"source code management",{"text":548,"config":603},{"href":111,"dataGaName":604,"dataGaLocation":469},"continuous integration & delivery",{"text":606,"config":607},"Value stream management",{"href":161,"dataGaName":608,"dataGaLocation":469},"value stream management",{"text":553,"config":610},{"href":611,"dataGaName":556,"dataGaLocation":469},"/solutions/gitops/",{"text":171,"config":613},{"href":173,"dataGaName":174,"dataGaLocation":469},{"text":615,"config":616},"Small business",{"href":178,"dataGaName":179,"dataGaLocation":469},{"text":618,"config":619},"Public sector",{"href":183,"dataGaName":184,"dataGaLocation":469},{"text":621,"config":622},"Education",{"href":623,"dataGaName":624,"dataGaLocation":469},"/solutions/education/","education",{"text":626,"config":627},"Financial services",{"href":628,"dataGaName":629,"dataGaLocation":469},"/solutions/finance/","financial services",{"title":191,"links":631},[632,634,636,638,641,643,645,647,649,651,653,655],{"text":203,"config":633},{"href":205,"dataGaName":206,"dataGaLocation":469},{"text":208,"config":635},{"href":210,"dataGaName":211,"dataGaLocation":469},{"text":213,"config":637},{"href":215,"dataGaName":216,"dataGaLocation":469},{"text":218,"config":639},{"href":220,"dataGaName":640,"dataGaLocation":469},"docs",{"text":241,"config":642},{"href":243,"dataGaName":244,"dataGaLocation":469},{"text":236,"config":644},{"href":238,"dataGaName":239,"dataGaLocation":469},{"text":251,"config":646},{"href":253,"dataGaName":254,"dataGaLocation":469},{"text":259,"config":648},{"href":261,"dataGaName":262,"dataGaLocation":469},{"text":264,"config":650},{"href":266,"dataGaName":267,"dataGaLocation":469},{"text":269,"config":652},{"href":271,"dataGaName":272,"dataGaLocation":469},{"text":274,"config":654},{"href":276,"dataGaName":277,"dataGaLocation":469},{"text":279,"config":656},{"href":281,"dataGaName":282,"dataGaLocation":469},{"title":293,"links":658},[659,661,663,665,667,669,671,675,680,682,684,686],{"text":300,"config":660},{"href":302,"dataGaName":295,"dataGaLocation":469},{"text":305,"config":662},{"href":307,"dataGaName":308,"dataGaLocation":469},{"text":313,"config":664},{"href":315,"dataGaName":316,"dataGaLocation":469},{"text":318,"config":666},{"href":320,"dataGaName":321,"dataGaLocation":469},{"text":323,"config":668},{"href":325,"dataGaName":326,"dataGaLocation":469},{"text":328,"config":670},{"href":330,"dataGaName":331,"dataGaLocation":469},{"text":672,"config":673},"Sustainability",{"href":674,"dataGaName":672,"dataGaLocation":469},"/sustainability/",{"text":676,"config":677},"Diversity, inclusion and belonging (DIB)",{"href":678,"dataGaName":679,"dataGaLocation":469},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":333,"config":681},{"href":335,"dataGaName":336,"dataGaLocation":469},{"text":343,"config":683},{"href":345,"dataGaName":346,"dataGaLocation":469},{"text":348,"config":685},{"href":350,"dataGaName":351,"dataGaLocation":469},{"text":687,"config":688},"Modern Slavery Transparency Statement",{"href":689,"dataGaName":690,"dataGaLocation":469},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":692},[693,696,699],{"text":694,"config":695},"Terms",{"href":521,"dataGaName":522,"dataGaLocation":469},{"text":697,"config":698},"Cookies",{"dataGaName":531,"dataGaLocation":469,"id":532,"isOneTrustButton":28},{"text":700,"config":701},"Privacy",{"href":526,"dataGaName":527,"dataGaLocation":469},[703],{"id":704,"title":9,"body":26,"config":705,"content":707,"description":26,"extension":25,"meta":711,"navigation":28,"path":712,"seo":713,"stem":714,"__hash__":715},"blogAuthors/en-us/blog/authors/sharon-gaudin.yml",{"template":706},"BlogAuthor",{"name":9,"config":708},{"headshot":709,"ctfId":710},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749663767/Blog/Author%20Headshots/sharongaudinheadshot.png","sgaudin",{},"/en-us/blog/authors/sharon-gaudin",{},"en-us/blog/authors/sharon-gaudin","lwl3tVS21sy4cT3hDh1caPfqWTJoyKj14Mm8B1cb8ME",[717,730,744],{"content":718,"config":728},{"title":719,"description":720,"authors":721,"heroImage":723,"date":724,"body":725,"category":11,"tags":726},"Teaching software development the easy way using GitLab","Learn how University of Washington lecturer Stephen G. Dame uses GitLab for Education to manage student assignments, distribute course materials, and provide inline code feedback at scale.\n",[722],"Rod Burns","https://res.cloudinary.com/about-gitlab-com/image/upload/v1749659537/Blog/Hero%20Images/display-article-image-0679-1800x945-fy26.png","2026-04-29","For instructors teaching software development, one of the biggest logistical challenges is assignment distribution and feedback at scale. How do you give large groups of students access to course materials, keep solution code private, and still deliver meaningful, contextual feedback without lots of administrative overhead?\n\nThe **[GitLab for Education program](https://about.gitlab.com/solutions/education/)** provides qualifying institutions with free access to **GitLab Ultimate**, enabling instructors to build professional-grade workflows that mirror real-world software development environments. In this article, you'll learn how Stephen G. Dame, a lecturer in the Computing and Software Systems department at the University of Washington, Bothell, uses simple workflows in GitLab to manage everything from course materials to student feedback across multiple classes.\n\n## From aerospace to academia: Bringing GitLab to the classroom\n\nDame came to academia with years of experience as a chief software engineer at Boeing Commercial Airplanes, where GitLab was used for aerospace projects. As an adjunct professor, he became an early advocate for GitLab within the university, joining the GitLab for Education program to access the full feature set needed to run structured, scalable course workflows.\n\n> **\"GitLab provides the greatest way to organize multiple classes, student assignments, lectures, and code samples through the use of Groups and Subgroups, which I found to be unique to GitLab compared to other repository platforms.\"**\n>\n> - Stephen G. Dame, University of Washington, Bothell\n\n## Set up groups: Build the right structure before writing a line of code\n\nThe foundation of an effective GitLab-based course is a well-planned group hierarchy. GitLab's **[Groups and Subgroups](https://docs.gitlab.com/tutorials/manage_user/#create-the-organization-parent-group-and-subgroups)** allow instructors to model the natural structure of a university department institution, course, and role with precise, inheritable permissions at every level.\n\nDame's structure places the university at the root (`UWTeaching`), with each course occupying its own subgroup (e.g. `css430`). Within each course sit repositories for `lecture-materials` and `code`, alongside dedicated Subgroups for `students` and `graders`. Instructor materials remain private, while student and grader subgroups are configured with controlled permissions so that assignment briefs and solutions are visible only to the right people.\n\n![Screenshot of GitLab group hierarchy — institution, course subgroup, and per-student subgroups](https://res.cloudinary.com/about-gitlab-com/image/upload/v1777463673/dpxfnitv76pdmvcqtgag.png)\n\nPermissions cascade downward through the hierarchy via **Manage > Members**, allowing Dame to add students to a course's `students` subgroup with `Reporter` access and an expiration date tied to the end of the academic quarter. Students can clone and pull from assignment repositories but cannot push — keeping solution code firmly under instructor control.\n\nStudents are guided to set up SSH keys across all their working environments (local machines, cloud shells, virtual machines) so they can clone repositories and receive weekly updates via `git pull`. They copy relevant code into their own private repositories to manage their own version history.\n\n**Tip for large classes:** For larger cohorts, adding students by hand is impractical. GitLab's REST API lets you automate subgroup creation and membership from a list of usernames. Below is a sample Python script that handles this:\n\n```python\n    import gitlab\n    from datetime import datetime\n\n    # Connect to your GitLab instance\n    gl = gitlab.Gitlab('https://gitlab.com', private_token='YOUR_PRIVATE_TOKEN')\n\n    # Target parent group ID (e.g., the ID for \"css430 > students\")\n    parent_group_id = 12345678\n\n    # Set expiration: typically the beginning of the next month after quarter end\n    expiry_date = '2025-01-01'\n\n    # List of collected student usernames\n    student_list = ['alice_css430', 'bob_css430', 'carol_css430', 'dave_css430', 'eve_css430']\n\n    for username in student_list:\n        try:\n            # 1. Create a personal subgroup for the student\n            subgroup = gl.groups.create({\n                'name': username,\n                'path': username,\n                'parent_id': parent_group_id,\n                'visibility': 'private'\n            })\n\n            # 2. Add student to the new subgroup with Expiration\n            user = gl.users.list(username=username)[0]\n            subgroup.members.create({\n                'user_id': user.id,\n                'access_level': gitlab.const.REPORTER_ACCESS,\n                'expires_at': expiry_date\n            })\n            print(f\"Success: Subgroup created and student added for {username}\")\n        except Exception as e:\n            print(f\"Error processing {username}: {e}\")\n```\nThere is also an [open source project that automates class management](https://gitlab.com/edu-docs/class-management-automation) published by GitLab that provides additional tooling for this workflow.\n## Give feedback where the work actually lives\n\nOnce the structure is in place, the feedback workflow is where GitLab's value becomes most apparent to students. Dame asks students to submit assignments by opening a **[merge request](https://docs.gitlab.com/user/project/merge_requests/)** in their repository. This gives instructors an immediate, clean diff of everything the student has written.\n![A GitLab merge request showing inline code comment function for an instructor](https://res.cloudinary.com/about-gitlab-com/image/upload/v1777467468/icclzyglbkwlvfysggbi.png)\nInstructors can click any line of code and leave an **inline comment** — not just flagging what is wrong, but explaining why, and pointing to what to look at next. Students receive this feedback in direct context with their code, which is far more actionable than a comment at the bottom of a submitted document.\n\n## Join GitLab for Education\n\nSetting up your first GitLab assignment takes some initial effort, but once the structure is in place it largely runs itself. The real payoff goes beyond organization: Students graduate having worked daily in an environment that mirrors professional software development, building habits around [version control](https://about.gitlab.com/topics/version-control/) and [code review](https://docs.gitlab.com/development/code_review/) rather than learning them as abstract concepts.\n\nIf you are just getting started, keep it simple. Begin with a single course group, one assignment template, and a basic pipeline. The structure will grow naturally alongside your confidence with the platform.\n\nMake sure to **[sign up for GitLab for Education](https://about.gitlab.com/solutions/education/join/)** so that you and your students can access all top-tier features, including unlimited reviewers on merge requests, additional compute minutes, and expanded storage.\n\n> [Apply to the GitLab for Education program today](https://about.gitlab.com/solutions/education/join/).",[624,727],"open source",{"featured":14,"template":15,"slug":729},"teaching-software-development-the-easy-way-using-gitlab",{"content":731,"config":742},{"description":732,"authors":733,"heroImage":735,"date":736,"title":737,"body":738,"category":11,"tags":739},"AI-generated code is 34% of development work. Discover how to balance productivity gains with quality, reliability, and security.",[734],"Manav Khurana","https://res.cloudinary.com/about-gitlab-com/image/upload/v1767982271/e9ogyosmuummq7j65zqg.png","2026-01-08","AI is reshaping DevSecOps: Attend GitLab Transcend to see what’s next","AI promises a step change in innovation velocity, but most software teams are hitting a wall. According to our latest [Global DevSecOps Report](https://about.gitlab.com/developer-survey/), AI-generated code now accounts for 34% of all development work. Yet 70% of DevSecOps professionals report that AI is making compliance management more difficult, and 76% say agentic AI will create unprecedented security challenges.\n\nThis is the AI paradox: AI accelerates coding, but software delivery slows down as teams struggle to test, secure, and deploy all that code.\n\n## Productivity gains meet workflow bottlenecks\nThe problem isn't AI itself. It's how software gets built today. The traditional DevSecOps lifecycle contains hundreds of small tasks that developers must navigate manually: updating tickets, running tests, requesting reviews, waiting for approvals, fixing merge conflicts, addressing security findings. These tasks drain an average of seven hours per week from every team member, according to our research.\n\nDevelopment teams are producing code faster than ever, but that code still crawls through fragmented toolchains, manual handoffs, and disconnected processes. In fact, 60% of DevSecOps teams use more than five tools for software development overall, and 49% use more than five AI tools. This fragmentation creates collaboration barriers, with 94% of DevSecOps professionals experiencing factors that limit collaboration in the software development lifecycle.\n\nThe answer isn't more tools. It's intelligent orchestration that brings software teams and their AI agents together across projects and release cycles, with enterprise-grade security, governance, and compliance built in.\n\n## Seeking deeper human-AI partnerships\nDevSecOps professionals don't want AI to take over — they want reliable partnerships. The vast majority (82%) say using agentic AI would increase their job satisfaction, and 43% envision an ideal future with a 50/50 split between human and AI contributions. They're ready to trust AI with 37% of their daily tasks without human review, particularly for documentation, test writing, and code reviews.\n\nWhat we heard resoundingly from DevSecOps professionals is that AI won't replace them; rather, it will fundamentally reshape their roles. 83% of DevSecOps professionals believe AI will significantly change their work within five years, and notably, 76% think this will create more engineering jobs, not fewer. As coding becomes easier with AI, engineers who can architect systems, ensure quality, and apply business context will be in high demand.\n\nCritically, 88% agree there are essential human qualities that AI will never fully replace, including creativity, innovation, collaboration, and strategic vision.\n\nSo how can organizations bridge the gap between AI’s promise and the reality of fragmented workflows?\n\n## Join us at GitLab Transcend: Explore how to drive real value with agentic AI\nOn February 10, 2026, GitLab will be hosting Transcend, where we'll reveal how intelligent orchestration transforms AI-powered software development. You'll get a first look at GitLab's upcoming product roadmap and learn how teams are solving real-world challenges by modernizing development workflows with AI.\n\nOrganizations winning in this new era balance AI adoption with security, compliance, and platform consolidation. AI offers genuine productivity gains when implemented thoughtfully — not by replacing human developers, but by freeing DevSecOps professionals to focus on strategic thinking and creative innovation.\n\n[Register for Transcend today](https://about.gitlab.com/events/transcend/virtual/) to secure your spot and discover how intelligent orchestration can help your software teams stay in flow.",[740,22,741],"AI/ML","security",{"featured":28,"template":15,"slug":743},"ai-is-reshaping-devsecops-attend-gitlab-transcend-to-see-whats-next",{"content":745,"config":756},{"title":746,"description":747,"authors":748,"heroImage":750,"date":751,"body":752,"category":11,"tags":753},"Atlassian ending Data Center as GitLab maintains deployment choice","As Atlassian transitions Data Center customers to cloud-only, GitLab presents a menu of deployment choices that map to business needs.",[749],"Emilio Salvador","https://res.cloudinary.com/about-gitlab-com/image/upload/v1750098354/Blog/Hero%20Images/Blog/Hero%20Images/blog-image-template-1800x945%20%281%29_5XrohmuWBNuqL89BxVUzWm_1750098354056.png","2025-10-07","Change is never easy, especially when it's not your choice. Atlassian's announcement that [all Data Center products will reach end-of-life by March 28, 2029](https://www.atlassian.com/blog/announcements/atlassian-ascend), means thousands of organizations must now reconsider their DevSecOps deployment and infrastructure. But you don't have to settle for deployment options that don't fit your needs. GitLab maintains your freedom to choose — whether you need self-managed for compliance, cloud for convenience, or hybrid for flexibility — all within a single AI-powered DevSecOps platform that respects your requirements.\n\nWhile other vendors force migrations to cloud-only architectures, GitLab remains committed to supporting the deployment choices that match your business needs. Whether you're managing sensitive government data, operating in air-gapped environments, or simply prefer the control of self-managed deployments, we understand that one size doesn't fit all.\n\n## The cloud isn't the answer for everyone\n\nFor the many companies that invested millions of dollars in Data Center deployments, including those that migrated to Data Center [after its Server products were discontinued](https://about.gitlab.com/blog/atlassian-server-ending-move-to-a-single-devsecops-platform/), this announcement represents more than a product sunset. It signals a fundamental shift away from customer-centric architecture choices, forcing enterprises into difficult positions: accept a deployment model that doesn't fit their needs, or find a vendor that respects their requirements.\n\nMany of the organizations requiring self-managed deployments represent some of the world's most important organizations: healthcare systems protecting patient data, financial institutions managing trillions in assets, government agencies safeguarding national security, and defense contractors operating in air-gapped environments.\n\nThese organizations don't choose self-managed deployments for convenience; they choose them for compliance, security, and sovereignty requirements that cloud-only architectures simply cannot meet. Organizations operating in closed environments with restricted or no internet access aren't exceptions — they represent a significant portion of enterprise customers across various industries.\n\n![GitLab vs. Atlassian comparison table](https://res.cloudinary.com/about-gitlab-com/image/upload/v1759928476/ynl7wwmkh5xyqhszv46m.jpg)\n\n## The real cost of forced cloud migration goes beyond dollars\n\nWhile cloud-only vendors frame mandatory migrations as \"upgrades,\" organizations face substantial challenges beyond simple financial costs:\n\n* **Lost integration capabilities:** Years of custom integrations with legacy systems, carefully crafted workflows, and enterprise-specific automations become obsolete. Organizations with deep integrations to legacy systems often find cloud migration technically infeasible.\n\n* **Regulatory constraints:** For organizations in regulated industries, cloud migration isn't just complex — it's often not permitted. Data residency requirements, air-gapped environments, and strict regulatory frameworks don't bend to vendor preferences. The absence of single-tenant solutions in many cloud-only approaches creates insurmountable compliance barriers.\n\n* **Productivity impacts:** Cloud-only architectures often require juggling multiple products: separate tools for planning, code management, CI/CD, and documentation. Each tool means another context switch, another integration to maintain, another potential point of failure. GitLab research shows [30% of developers spend at least 50% of their job maintaining and/or integrating their DevSecOps toolchain](https://about.gitlab.com/developer-survey/). Fragmented architectures exacerbate this challenge rather than solving it.\n\n## GitLab offers choice, commitment, and consolidation\n\nEnterprise customers deserve a trustworthy technology partner. That's why we've committed to supporting a range of deployment options — whether you need on-premises for compliance, hybrid for flexibility, or cloud for convenience, the choice remains yours. That commitment continues with [GitLab Duo](https://about.gitlab.com/gitlab-duo-agent-platform/), our AI solution that supports developers at every stage of their workflow.\n\nBut we offer more than just deployment flexibility. While other vendors might force you to cobble together their products into a fragmented toolchain, GitLab provides everything in a **comprehensive AI-native DevSecOps platform**. Source code management, CI/CD, security scanning, Agile planning, and documentation are all managed within a single application and a single vendor relationship.\n\nThis isn't theoretical. When Airbus and [Iron Mountain](https://about.gitlab.com/customers/iron-mountain/) evaluated their existing fragmented toolchains, they consistently identified challenges: poor user experience, missing functionalities like built-in security scanning and review apps, and management complexity from plugin troubleshooting. **These aren't minor challenges; they're major blockers for modern software delivery.**\n\n## Your migration path: Simpler than you think\n\nWe've helped thousands of organizations migrate from other vendors, and we've built the tools and expertise to make your transition smooth:\n\n* **Automated migration tools:** Our [Bitbucket Server importer](https://docs.gitlab.com/user/import/bitbucket_server/) brings over repositories, pull requests, comments, and even Large File Storage (LFS) objects. For Jira, our [built-in importer](https://docs.gitlab.com/user/project/import/jira/) handles issues, descriptions, and labels, with professional services available for complex migrations.\n\n* **Proven at scale:** A 500 GiB repository with 13,000 pull requests, 10,000 branches, and 7,000 tags is likely to [take just 8 hours to migrate](https://docs.gitlab.com/user/import/bitbucket_server/) from Bitbucket to GitLab using parallel processing.\n\n* **Immediate ROI:** A [Forrester Consulting Total Economic Impact™ study commissioned by GitLab](https://about.gitlab.com/resources/study-forrester-tei-gitlab-ultimate/) found that investing in GitLab Ultimate confirms these benefits translate to real bottom-line impact, with a three-year 483% ROI, 5x time saved in security related activities, and 25% savings in software toolchain costs.\n\n## Start your journey to a unified DevSecOps platform\n\nForward-thinking organizations aren't waiting for vendor-mandated deadlines. They're evaluating alternatives now, while they have time to migrate thoughtfully to platforms that protect their investments and deliver on promises.\n\nOrganizations invest in self-managed deployments because they need control, compliance, and customization. When vendors deprecate these capabilities, they remove not just features but the fundamental ability to choose environments matching business requirements.\n\nModern DevSecOps platforms should offer complete functionality that respects deployment needs, consolidates toolchains, and accelerates software delivery, without forcing compromises on security or data sovereignty.\n\n[Talk to our sales team](https://about.gitlab.com/sales/) today about your migration options, or explore our [comprehensive migration resources](https://about.gitlab.com/move-to-gitlab-from-atlassian/) to see how thousands of organizations have already made the switch.\n\nYou also can [try GitLab Ultimate with GitLab Duo Enterprise](https://about.gitlab.com/free-trial/devsecops/) for free for 30 days to see what a unified DevSecOps platform can do for your organization.",[575,568,754,755],"product","features",{"featured":28,"template":15,"slug":757},"atlassian-ending-data-center-as-gitlab-maintains-deployment-choice",{"promotions":759},[760,774,785,796],{"id":761,"categories":762,"header":764,"text":765,"button":766,"image":771},"ai-modernization",[763],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":767,"config":768},"Get your AI maturity score",{"href":769,"dataGaName":770,"dataGaLocation":244},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":772},{"src":773},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":775,"categories":776,"header":777,"text":765,"button":778,"image":782},"devops-modernization",[754,11],"Are you just managing tools or shipping innovation?",{"text":779,"config":780},"Get your DevOps maturity score",{"href":781,"dataGaName":770,"dataGaLocation":244},"/assessments/devops-modernization-assessment/",{"config":783},{"src":784},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":786,"categories":787,"header":788,"text":765,"button":789,"image":793},"security-modernization",[741],"Are you trading speed for security?",{"text":790,"config":791},"Get your security maturity score",{"href":792,"dataGaName":770,"dataGaLocation":244},"/assessments/security-modernization-assessment/",{"config":794},{"src":795},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":797,"paths":798,"header":801,"text":802,"button":803,"image":808},"github-azure-migration",[799,800],"migration-from-azure-devops-to-gitlab","integrating-azure-devops-scm-and-gitlab","Is your team ready for GitHub's Azure move?","GitHub is already rebuilding around Azure. Find out what it means for you.",{"text":804,"config":805},"See how GitLab compares to GitHub",{"href":806,"dataGaName":807,"dataGaLocation":244},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":809},{"src":784},{"header":811,"blurb":812,"button":813,"secondaryButton":818},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":814,"config":815},"Get your free trial",{"href":816,"dataGaName":51,"dataGaLocation":817},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":507,"config":819},{"href":55,"dataGaName":56,"dataGaLocation":817},1777493586452]