[{"data":1,"prerenderedAt":822},["ShallowReactive",2],{"/en-us/blog/oidc":3,"navigation-en-us":42,"banner-en-us":453,"footer-en-us":463,"blog-post-authors-en-us-Dov Hershkovitch":703,"blog-related-posts-en-us-oidc":717,"blog-promotions-en-us":760,"next-steps-en-us":812},{"id":4,"title":5,"authorSlugs":6,"authors":8,"body":10,"category":11,"categorySlug":11,"config":12,"content":16,"date":20,"description":17,"extension":26,"externalUrl":27,"featured":14,"heroImage":19,"isFeatured":14,"meta":28,"navigation":29,"path":30,"publishedDate":20,"rawbody":31,"seo":32,"slug":13,"stem":36,"tagSlugs":37,"tags":40,"template":15,"updatedDate":27,"__hash__":41},"blogPosts/en-us/blog/oidc.yml","Secure GitLab CI/CD workflows using OIDC JWT on a DevSecOps platform",[7],"dov-hershkovitch",[9],"Dov Hershkovitch","\n\nSecuring CI/CD workflows can be challenging. This blog post walks you through the problem validation, explores the JWT token technology and how it can be used with OIDC authentication, and discusses implementation challenges with authorization realms. You will learn about the current possibilities and future plans with GitLab 16.0.\n\n### Variables vs. secrets\nVariables are an efficient way to control and inject parameters into your jobs and pipelines, making managing and configuring the CI/CD workflows easier. You can read more about [how to use CI/CD variables](https://about.gitlab.com/blog/demystifying-ci-cd-variables/). An extra layer of security on top of variables to mask and protect, for now, is our “best-effort” to prevent sensitive variables from being accidentally revealed. However, variables are not a drop-in replacement for secrets. [Securing secrets natively](https://gitlab.com/gitlab-org/gitlab/-/issues/217355) is a solution that GitLab aspires to provide. Meanwhile, we recommend storing sensitive information in a dedicated secrets management solution. As a company, we will provide you abilities to integrate and retrieve secrets as part of your CI/CD workflows.\n\n## Security shifting left\nSensitive information like passwords, secret tokens, or shared IDs required to access tools and platforms need to be securely stored. They must also be highly available to their owners and the teams who use them. There are various secrets management solutions and frameworks available. They have addressed one problem but created new problems. For example: \"Which tool is right for our needs?\" More importantly, in software development: \"What's the best way to integrate this into our DevOps processes so that we're secure but still operating as efficiently as possible?\" Ignoring the security protocols in your organization is not an option. However, sensitive information should be stored as securely as possible. Something as simple as an access token stored in plain text can lead to security leaks and business incidents in the worst-case scenarios.\n\n## Initial support for JWT\nThe [JSON Web Token (JWT)](https://en.wikipedia.org/wiki/JSON_Web_Token) aims to build the integration bridge as an open standard for security claims exchange. It is a signed, short-lived, contextualized token that allows everyone to implement authentication between different products securely. The JWT consists of three parts: a header, a payload, and a signature.\n\n- The header represents the type of the token and the encryption algorithm.\n- The signature ensures that the token hasn't been altered.\n- The payload comprises a series of claims representing the information exchanged between two parties, which includes information about a GitLab user (ID, email, login) and the pipeline information (pipeline ID, job ID, environment, and more).\n\n_Example of GitLab JWT payload_\n\n```json\n{\n  \"jti\": \"c82eeb0c-5c6f-4a33-abf5-4c474b92b558\",\n  \"iss\": \"gitlab.example.com\",\n  \"iat\": 1585710286,\n  \"nbf\": 1585798372,\n  \"exp\": 1585713886,\n  \"sub\": \"job_1212\",\n  \"namespace_id\": \"1\",\n  \"namespace_path\": \"mygroup\",\n  \"project_id\": \"22\",\n  \"project_path\": \"mygroup/myproject\",\n  \"user_id\": \"42\",\n  \"user_login\": \"myuser\",\n  \"user_email\": \"myuser@example.com\",\n  \"pipeline_id\": \"1212\",\n  \"pipeline_source\": \"web\",\n  \"job_id\": \"1212\",\n  \"ref\": \"auto-deploy-2020-04-01\",\n  \"ref_type\": \"branch\",\n  \"ref_protected\": \"true\",\n  \"environment\": \"production\",\n  \"environment_protected\": \"true\"\n}\n```\nUsing this information (called \"claims\"), you can implement an authentication condition where the token will get rejected if one of those claims does not match. You can use this to restrict access to only the authorized users and jobs in your pipelines.\n\nGitLab 12.10 added [initial support for JWT token-based connections](https://docs.gitlab.com/releases/#retrieve-cicd-secrets-from-hashicorp-vault), which was later [enhanced](https://docs.gitlab.com/releases/#use-hashicorp-vault-secrets-in-ci-jobs) with the `secrets:` keyword, as well as the `CI_JOB_JWT` predefined CI/CD variable, which is automatically injected into every job in a pipeline. This implementation was restricted to Hashicorp Vault, and users can use it to read secrets directly from the vault as part of their CI/CD workflow.\n### OIDC (JWT Version 2)\nThe logic we used to build the initial support for JWT opened up the possibility of connecting to other providers as well, but the first iteration was still restricted to Hashicorp Vault users.\n\nThis problem was addressed in GitLab 14.7 when we [released](https://docs.gitlab.com/releases/#openid-connect-support-for-gitlab-cicd) the first \"Alpha\" version of JWT V2, which provided [Open ID Connect (OIDC)](https://openid.net/connect/) support for CI/CD.\n\nOIDC is an identity layer implemented on top of the JSON web token. You can securely authenticate against many products and services that implement OIDC, including AWS, GCP, and many more, making better use of the token's potential. Similar to our first JWT iteration, we added another [predefined CI/CD variable](https://docs.gitlab.com/ci/variables/predefined_variables/) `CI_JOB_JWT_V2` which is also automatically injected into every job in a CI/CD pipeline.\n\n### Securely store your secrets\nYour software supply chain should include everything needed to deliver and run your software. Securing your supply chain means you need to secure your software and the surrounding (cloud-native) infrastructure. In [GitLab 15.9](https://docs.gitlab.com/releases/), we've added additional layers of protection to move our OIDC token from an Experiment to General Availability, increasing the security of your CI/CD workflows.\n\n\n#### Opt-in JWT token\nJSON web tokens (V1 and V2) are stored in CI/CD variables, which are injected automatically into all jobs in a CI/CD pipeline. However, it is likely most jobs in your pipeline do not need the token. In addition to the inefficiency of injecting unused tokens into all jobs in a pipeline, there is a potential security vulnerability. All it takes is one compromised job for this token to be leaked and used by an attacker to retrieve sensitive information from your organization. To minimize this risk, we've added the ability to restrict the token variable from all jobs in your pipeline and expose it only to the specific jobs that need it.\n\nTo declare the JSON web token in a job that needs it, configure the job in the `.gitlab-ci.yml` configuration file following this example:\n\n```yaml\njob_name:\n  id_token:\n    MY_JOB_JWT: # or any other variable name\n  ...\n\n```\n\nYou can minimize the token exposure across your pipeline, but ensure it is available to the jobs that require it.\n\n#### Audience claim (`aud:`)\nClaims constitute the payload part of a JSON web token and represent a set of information exchanged between two parties. The JWT standard distinguishes between reserved, public, and private claims.\n\nThe audience (`aud:`) claim is a reserved claim, which identifies the audience that the JWT is intended for (the target of the token). In other words, which services, APIs, or products should accept this token. If the audience claim does not match, the token is rejected, so the audience claim is an essential part of software supply chain security.\n\nThe option to configure the audience claim is done in the CI/CD configuration when [declaring the usage of the JWT token](https://docs.gitlab.com/ci/secrets/id_token_authentication/#id-tokens), if we'll continue from the previous example:\n\n```yaml\njob_name:\n  id_token:\n    MY_JOB_JWT: # or any other variable name\n        aud: \"...\" # mandatory field\n  script:\n    - my-authentication-script.sh MY_JOB_JWT….. # use the declared variables in a script\n  ```\n\nConfiguring the audience claim is mandatory for Vault users that leverage the [GitLab/Vault native integration](https://docs.gitlab.com/ci/secrets/#use-vault-secrets-in-a-ci-job) (using the 'secrets:' keyword).\n\n```yaml\njob_name:\n  secrets:\n    VAULT_JWT_1: # or any other variable name\n      id_token:\n        aud: 'devs' # audience claim configuration\n    STAGING_DATABASE_PASSWORD: # VAULT_JWT_1 is the token to be used\n      vault: staging/db/password@ops\n\n```\n\n### Breaking changes and backward compatibility\nWe understand the increasing demand to secure your software supply chain. We recognize that many of our current users already use the JWT in what will soon be the \"old JWT method\" (V1). To mitigate this conflict, we've decided that moving to the new (OIDC) JWT method is optional until the next major release (GitLab 16.0). To use the new (OIDC) token, users must opt-in to this change from the UI settings and update the pipeline configuration, as explained in the previous sections. Users can continue using the Experiment or the \"old method\" until GitLab 16.0. (At that point, only the \"new\" (OIDC) JWT token and method will be available.)\n\nSeveral breaking changes were announced for both [Vault users](https://docs.gitlab.com/update/deprecations/#hashicorp-vault-integration-will-no-longer-use-ci_job_jwt-by-default) and [users of the JWT \"old\" methods](https://docs.gitlab.com/update/deprecations/#old-versions-of-json-web-tokens-are-deprecated). Those changes are scheduled for GitLab 16.0.\n\n## Three ways to use the JWT token\nThere are three ways to use a JWT to authenticate against different products in your CI/CD pipeline:\n- The \"old\" method, using the `secrets:` keyword and the `CI_JOB_JWT` variable, which is mainly used to integrate with Hashicorp Vault.\n- An \"Alpha\" version that uses the `CI_JOB_JWT_V2` OIDC token to integrate with different cloud providers.\n- A production-ready OIDC token, which is a secured version of the `CI_JOB_JWT_V2` token, used to authenticate with a variety of different products, like Vault, GCP, AWS, and so on.\n\nAll three methods are available until the next major version (GitLab 16.0). At that point, only the secured OIDC token will be available.\n\nTo prepare for this change, you should:\n\n1. Configure your pipelines to use the fully configurable and more secure [id_token](https://docs.gitlab.com/ci/yaml/#id_tokens) keyword.\n2. Enable the [Limit JSON Web Token (JWT) access setting](https://docs.gitlab.com/ci/secrets/id_token_authentication/#enable-automatic-id-token-authentication), which prevents the old tokens from being exposed to any jobs. (This setting will be permanently enabled for all projects in GitLab 16.0).\n3. If you use GitLab/Hashicorp native integration (using the [secrets:vault](https://docs.gitlab.com/ci/yaml/#secretsvault) keyword), ensure the bound audience is prefixed with `https://`.\n\nThis should ensure a smooth transition to [GitLab 16.0](/releases/whats-new/) without breaking your existing workflows.\n\n\n","devsecops",{"slug":13,"featured":14,"template":15},"oidc",false,"BlogPost",{"title":5,"description":17,"authors":18,"heroImage":19,"date":20,"body":10,"category":11,"tags":21},"Learn a new method to authenticate using JWT to increase the security of CI/CD workflows.",[9],"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749667094/Blog/Hero%20Images/container-security.jpg","2023-02-28",[22,23,24,25],"tutorial","DevSecOps","CI","CD","yml",null,{},true,"/en-us/blog/oidc","seo:\n  title: Secure GitLab CI/CD workflows using OIDC JWT on a DevSecOps platform\n  description: >-\n    Learn a new method to authenticate using JWT to increase the security of\n    CI/CD workflows.\n  ogTitle: Secure GitLab CI/CD workflows using OIDC JWT on a DevSecOps platform\n  ogDescription: >-\n    Learn a new method to authenticate using JWT to increase the security of\n    CI/CD workflows.\n  noIndex: false\n  ogImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749667094/Blog/Hero%20Images/container-security.jpg\n  ogUrl: https://about.gitlab.com/blog/oidc\n  ogSiteName: https://about.gitlab.com\n  ogType: article\n  canonicalUrls: https://about.gitlab.com/blog/oidc\ncontent:\n  title: Secure GitLab CI/CD workflows using OIDC JWT on a DevSecOps platform\n  description: >-\n    Learn a new method to authenticate using JWT to increase the security of\n    CI/CD workflows.\n  authors:\n    - Dov Hershkovitch\n  heroImage: >-\n    https://res.cloudinary.com/about-gitlab-com/image/upload/v1749667094/Blog/Hero%20Images/container-security.jpg\n  date: '2023-02-28'\n  body: >+\n\n\n    Securing CI/CD workflows can be challenging. This blog post walks you\n    through the problem validation, explores the JWT token technology and how it\n    can be used with OIDC authentication, and discusses implementation\n    challenges with authorization realms. You will learn about the current\n    possibilities and future plans with GitLab 16.0.\n\n\n    ### Variables vs. secrets\n\n    Variables are an efficient way to control and inject parameters into your\n    jobs and pipelines, making managing and configuring the CI/CD workflows\n    easier. You can read more about [how to use CI/CD\n    variables](https://about.gitlab.com/blog/demystifying-ci-cd-variables/). An\n    extra layer of security on top of variables to mask and protect, for now, is\n    our “best-effort” to prevent sensitive variables from being accidentally\n    revealed. However, variables are not a drop-in replacement for secrets.\n    [Securing secrets\n    natively](https://gitlab.com/gitlab-org/gitlab/-/issues/217355) is a\n    solution that GitLab aspires to provide. Meanwhile, we recommend storing\n    sensitive information in a dedicated secrets management solution. As a\n    company, we will provide you abilities to integrate and retrieve secrets as\n    part of your CI/CD workflows.\n\n\n    ## Security shifting left\n\n    Sensitive information like passwords, secret tokens, or shared IDs required\n    to access tools and platforms need to be securely stored. They must also be\n    highly available to their owners and the teams who use them. There are\n    various secrets management solutions and frameworks available. They have\n    addressed one problem but created new problems. For example: \"Which tool is\n    right for our needs?\" More importantly, in software development: \"What's the\n    best way to integrate this into our DevOps processes so that we're secure\n    but still operating as efficiently as possible?\" Ignoring the security\n    protocols in your organization is not an option. However, sensitive\n    information should be stored as securely as possible. Something as simple as\n    an access token stored in plain text can lead to security leaks and business\n    incidents in the worst-case scenarios.\n\n\n    ## Initial support for JWT\n\n    The [JSON Web Token (JWT)](https://en.wikipedia.org/wiki/JSON_Web_Token)\n    aims to build the integration bridge as an open standard for security claims\n    exchange. It is a signed, short-lived, contextualized token that allows\n    everyone to implement authentication between different products securely.\n    The JWT consists of three parts: a header, a payload, and a signature.\n\n\n    - The header represents the type of the token and the encryption algorithm.\n\n    - The signature ensures that the token hasn't been altered.\n\n    - The payload comprises a series of claims representing the information\n    exchanged between two parties, which includes information about a GitLab\n    user (ID, email, login) and the pipeline information (pipeline ID, job ID,\n    environment, and more).\n\n\n    _Example of GitLab JWT payload_\n\n\n    ```json\n\n    {\n      \"jti\": \"c82eeb0c-5c6f-4a33-abf5-4c474b92b558\",\n      \"iss\": \"gitlab.example.com\",\n      \"iat\": 1585710286,\n      \"nbf\": 1585798372,\n      \"exp\": 1585713886,\n      \"sub\": \"job_1212\",\n      \"namespace_id\": \"1\",\n      \"namespace_path\": \"mygroup\",\n      \"project_id\": \"22\",\n      \"project_path\": \"mygroup/myproject\",\n      \"user_id\": \"42\",\n      \"user_login\": \"myuser\",\n      \"user_email\": \"myuser@example.com\",\n      \"pipeline_id\": \"1212\",\n      \"pipeline_source\": \"web\",\n      \"job_id\": \"1212\",\n      \"ref\": \"auto-deploy-2020-04-01\",\n      \"ref_type\": \"branch\",\n      \"ref_protected\": \"true\",\n      \"environment\": \"production\",\n      \"environment_protected\": \"true\"\n    }\n\n    ```\n\n    Using this information (called \"claims\"), you can implement an\n    authentication condition where the token will get rejected if one of those\n    claims does not match. You can use this to restrict access to only the\n    authorized users and jobs in your pipelines.\n\n\n    GitLab 12.10 added [initial support for JWT token-based\n    connections](https://docs.gitlab.com/releases/#retrieve-cicd-secrets-from-hashicorp-vault),\n    which was later\n    [enhanced](https://docs.gitlab.com/releases/#use-hashicorp-vault-secrets-in-ci-jobs)\n    with the `secrets:` keyword, as well as the `CI_JOB_JWT` predefined CI/CD\n    variable, which is automatically injected into every job in a pipeline. This\n    implementation was restricted to Hashicorp Vault, and users can use it to\n    read secrets directly from the vault as part of their CI/CD workflow.\n\n    ### OIDC (JWT Version 2)\n\n    The logic we used to build the initial support for JWT opened up the\n    possibility of connecting to other providers as well, but the first\n    iteration was still restricted to Hashicorp Vault users.\n\n\n    This problem was addressed in GitLab 14.7 when we\n    [released](https://docs.gitlab.com/releases/#openid-connect-support-for-gitlab-cicd)\n    the first \"Alpha\" version of JWT V2, which provided [Open ID Connect\n    (OIDC)](https://openid.net/connect/) support for CI/CD.\n\n\n    OIDC is an identity layer implemented on top of the JSON web token. You can\n    securely authenticate against many products and services that implement\n    OIDC, including AWS, GCP, and many more, making better use of the token's\n    potential. Similar to our first JWT iteration, we added another [predefined\n    CI/CD\n    variable](https://docs.gitlab.com/ci/variables/predefined_variables/)\n    `CI_JOB_JWT_V2` which is also automatically injected into every job in a\n    CI/CD pipeline.\n\n\n    ### Securely store your secrets\n\n    Your software supply chain should include everything needed to deliver and\n    run your software. Securing your supply chain means you need to secure your\n    software and the surrounding (cloud-native) infrastructure. In [GitLab\n    15.9](https://docs.gitlab.com/releases/),\n    we've added additional layers of protection to move our OIDC token from an\n    Experiment to General Availability, increasing the security of your CI/CD\n    workflows.\n\n\n\n    #### Opt-in JWT token\n\n    JSON web tokens (V1 and V2) are stored in CI/CD variables, which are\n    injected automatically into all jobs in a CI/CD pipeline. However, it is\n    likely most jobs in your pipeline do not need the token. In addition to the\n    inefficiency of injecting unused tokens into all jobs in a pipeline, there\n    is a potential security vulnerability. All it takes is one compromised job\n    for this token to be leaked and used by an attacker to retrieve sensitive\n    information from your organization. To minimize this risk, we've added the\n    ability to restrict the token variable from all jobs in your pipeline and\n    expose it only to the specific jobs that need it.\n\n\n    To declare the JSON web token in a job that needs it, configure the job in\n    the `.gitlab-ci.yml` configuration file following this example:\n\n\n    ```yaml\n\n    job_name:\n      id_token:\n        MY_JOB_JWT: # or any other variable name\n      ...\n\n    ```\n\n\n    You can minimize the token exposure across your pipeline, but ensure it is\n    available to the jobs that require it.\n\n\n    #### Audience claim (`aud:`)\n\n    Claims constitute the payload part of a JSON web token and represent a set\n    of information exchanged between two parties. The JWT standard distinguishes\n    between reserved, public, and private claims.\n\n\n    The audience (`aud:`) claim is a reserved claim, which identifies the\n    audience that the JWT is intended for (the target of the token). In other\n    words, which services, APIs, or products should accept this token. If the\n    audience claim does not match, the token is rejected, so the audience claim\n    is an essential part of software supply chain security.\n\n\n    The option to configure the audience claim is done in the CI/CD\n    configuration when [declaring the usage of the JWT\n    token](https://docs.gitlab.com/ci/secrets/id_token_authentication/#id-tokens),\n    if we'll continue from the previous example:\n\n\n    ```yaml\n\n    job_name:\n      id_token:\n        MY_JOB_JWT: # or any other variable name\n            aud: \"...\" # mandatory field\n      script:\n        - my-authentication-script.sh MY_JOB_JWT….. # use the declared variables in a script\n      ```\n\n    Configuring the audience claim is mandatory for Vault users that leverage\n    the [GitLab/Vault native\n    integration](https://docs.gitlab.com/ci/secrets/#use-vault-secrets-in-a-ci-job)\n    (using the 'secrets:' keyword).\n\n\n    ```yaml\n\n    job_name:\n      secrets:\n        VAULT_JWT_1: # or any other variable name\n          id_token:\n            aud: 'devs' # audience claim configuration\n        STAGING_DATABASE_PASSWORD: # VAULT_JWT_1 is the token to be used\n          vault: staging/db/password@ops\n\n    ```\n\n\n    ### Breaking changes and backward compatibility\n\n    We understand the increasing demand to secure your software supply chain. We\n    recognize that many of our current users already use the JWT in what will\n    soon be the \"old JWT method\" (V1). To mitigate this conflict, we've decided\n    that moving to the new (OIDC) JWT method is optional until the next major\n    release (GitLab 16.0). To use the new (OIDC) token, users must opt-in to\n    this change from the UI settings and update the pipeline configuration, as\n    explained in the previous sections. Users can continue using the Experiment\n    or the \"old method\" until GitLab 16.0. (At that point, only the \"new\" (OIDC)\n    JWT token and method will be available.)\n\n\n    Several breaking changes were announced for both [Vault\n    users](https://docs.gitlab.com/update/deprecations/#hashicorp-vault-integration-will-no-longer-use-ci_job_jwt-by-default)\n    and [users of the JWT \"old\"\n    methods](https://docs.gitlab.com/update/deprecations/#old-versions-of-json-web-tokens-are-deprecated).\n    Those changes are scheduled for GitLab 16.0.\n\n\n    ## Three ways to use the JWT token\n\n    There are three ways to use a JWT to authenticate against different products\n    in your CI/CD pipeline:\n\n    - The \"old\" method, using the `secrets:` keyword and the `CI_JOB_JWT`\n    variable, which is mainly used to integrate with Hashicorp Vault.\n\n    - An \"Alpha\" version that uses the `CI_JOB_JWT_V2` OIDC token to integrate\n    with different cloud providers.\n\n    - A production-ready OIDC token, which is a secured version of the\n    `CI_JOB_JWT_V2` token, used to authenticate with a variety of different\n    products, like Vault, GCP, AWS, and so on.\n\n\n    All three methods are available until the next major version (GitLab 16.0).\n    At that point, only the secured OIDC token will be available.\n\n\n    To prepare for this change, you should:\n\n\n    1. Configure your pipelines to use the fully configurable and more secure\n    [id_token](https://docs.gitlab.com/ci/yaml/#id_tokens) keyword.\n\n    2. Enable the [Limit JSON Web Token (JWT) access\n    setting](https://docs.gitlab.com/ci/secrets/id_token_authentication/#enable-automatic-id-token-authentication),\n    which prevents the old tokens from being exposed to any jobs. (This setting\n    will be permanently enabled for all projects in GitLab 16.0).\n\n    3. If you use GitLab/Hashicorp native integration (using the\n    [secrets:vault](https://docs.gitlab.com/ci/yaml/#secretsvault) keyword),\n    ensure the bound audience is prefixed with `https://`.\n\n\n    This should ensure a smooth transition to [GitLab\n    16.0](/releases/whats-new/) without breaking your existing workflows.\n\n\n  category: devsecops\n  tags:\n    - tutorial\n    - DevSecOps\n    - CI\n    - CD\nconfig:\n  slug: oidc\n  featured: false\n  template: BlogPost\n",{"title":5,"description":17,"ogTitle":5,"ogDescription":17,"noIndex":14,"ogImage":19,"ogUrl":33,"ogSiteName":34,"ogType":35,"canonicalUrls":33},"https://about.gitlab.com/blog/oidc","https://about.gitlab.com","article","en-us/blog/oidc",[22,11,38,39],"ci","cd",[22,23,24,25],"h-92DJ0xverIcLZpSESgIQhO2-q29_zVYH-13H7AbSQ",{"data":43},{"logo":44,"freeTrial":49,"sales":54,"login":59,"items":64,"search":373,"minimal":404,"duo":423,"switchNav":432,"pricingDeployment":443},{"config":45},{"href":46,"dataGaName":47,"dataGaLocation":48},"/","gitlab logo","header",{"text":50,"config":51},"Get free trial",{"href":52,"dataGaName":53,"dataGaLocation":48},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com&glm_content=default-saas-trial/","free trial",{"text":55,"config":56},"Talk to sales",{"href":57,"dataGaName":58,"dataGaLocation":48},"/sales/","sales",{"text":60,"config":61},"Sign in",{"href":62,"dataGaName":63,"dataGaLocation":48},"https://gitlab.com/users/sign_in/","sign in",[65,92,187,192,294,354],{"text":66,"config":67,"cards":69},"Platform",{"dataNavLevelOne":68},"platform",[70,76,84],{"title":66,"description":71,"link":72},"The intelligent orchestration platform for DevSecOps",{"text":73,"config":74},"Explore our Platform",{"href":75,"dataGaName":68,"dataGaLocation":48},"/platform/",{"title":77,"description":78,"link":79},"GitLab Duo Agent Platform","Agentic AI for the entire software lifecycle",{"text":80,"config":81},"Meet GitLab Duo",{"href":82,"dataGaName":83,"dataGaLocation":48},"/gitlab-duo-agent-platform/","gitlab duo agent platform",{"title":85,"description":86,"link":87},"Why GitLab","See the top reasons enterprises choose GitLab",{"text":88,"config":89},"Learn more",{"href":90,"dataGaName":91,"dataGaLocation":48},"/why-gitlab/","why gitlab",{"text":93,"left":29,"config":94,"link":96,"lists":100,"footer":169},"Product",{"dataNavLevelOne":95},"solutions",{"text":97,"config":98},"View all Solutions",{"href":99,"dataGaName":95,"dataGaLocation":48},"/solutions/",[101,125,148],{"title":102,"description":103,"link":104,"items":109},"Automation","CI/CD and automation to accelerate deployment",{"config":105},{"icon":106,"href":107,"dataGaName":108,"dataGaLocation":48},"AutomatedCodeAlt","/solutions/delivery-automation/","automated software delivery",[110,114,117,121],{"text":111,"config":112},"CI/CD",{"href":113,"dataGaLocation":48,"dataGaName":111},"/solutions/continuous-integration/",{"text":77,"config":115},{"href":82,"dataGaLocation":48,"dataGaName":116},"gitlab duo agent platform - product menu",{"text":118,"config":119},"Source Code Management",{"href":120,"dataGaLocation":48,"dataGaName":118},"/solutions/source-code-management/",{"text":122,"config":123},"Automated Software Delivery",{"href":107,"dataGaLocation":48,"dataGaName":124},"Automated software delivery",{"title":126,"description":127,"link":128,"items":133},"Security","Deliver code faster without compromising security",{"config":129},{"href":130,"dataGaName":131,"dataGaLocation":48,"icon":132},"/solutions/application-security-testing/","security and compliance","ShieldCheckLight",[134,138,143],{"text":135,"config":136},"Application Security Testing",{"href":130,"dataGaName":137,"dataGaLocation":48},"Application security testing",{"text":139,"config":140},"Software Supply Chain Security",{"href":141,"dataGaLocation":48,"dataGaName":142},"/solutions/supply-chain/","Software supply chain security",{"text":144,"config":145},"Software Compliance",{"href":146,"dataGaName":147,"dataGaLocation":48},"/solutions/software-compliance/","software compliance",{"title":149,"link":150,"items":155},"Measurement",{"config":151},{"icon":152,"href":153,"dataGaName":154,"dataGaLocation":48},"DigitalTransformation","/solutions/visibility-measurement/","visibility and measurement",[156,160,164],{"text":157,"config":158},"Visibility & Measurement",{"href":153,"dataGaLocation":48,"dataGaName":159},"Visibility and Measurement",{"text":161,"config":162},"Value Stream Management",{"href":163,"dataGaLocation":48,"dataGaName":161},"/solutions/value-stream-management/",{"text":165,"config":166},"Analytics & Insights",{"href":167,"dataGaLocation":48,"dataGaName":168},"/solutions/analytics-and-insights/","Analytics and insights",{"title":170,"items":171},"GitLab for",[172,177,182],{"text":173,"config":174},"Enterprise",{"href":175,"dataGaLocation":48,"dataGaName":176},"/enterprise/","enterprise",{"text":178,"config":179},"Small Business",{"href":180,"dataGaLocation":48,"dataGaName":181},"/small-business/","small business",{"text":183,"config":184},"Public Sector",{"href":185,"dataGaLocation":48,"dataGaName":186},"/solutions/public-sector/","public sector",{"text":188,"config":189},"Pricing",{"href":190,"dataGaName":191,"dataGaLocation":48,"dataNavLevelOne":191},"/pricing/","pricing",{"text":193,"config":194,"link":196,"lists":200,"feature":285},"Resources",{"dataNavLevelOne":195},"resources",{"text":197,"config":198},"View all resources",{"href":199,"dataGaName":195,"dataGaLocation":48},"/resources/",[201,234,257],{"title":202,"items":203},"Getting started",[204,209,214,219,224,229],{"text":205,"config":206},"Install",{"href":207,"dataGaName":208,"dataGaLocation":48},"/install/","install",{"text":210,"config":211},"Quick start guides",{"href":212,"dataGaName":213,"dataGaLocation":48},"/get-started/","quick setup checklists",{"text":215,"config":216},"Learn",{"href":217,"dataGaLocation":48,"dataGaName":218},"https://university.gitlab.com/","learn",{"text":220,"config":221},"Product documentation",{"href":222,"dataGaName":223,"dataGaLocation":48},"https://docs.gitlab.com/","product documentation",{"text":225,"config":226},"Best practice videos",{"href":227,"dataGaName":228,"dataGaLocation":48},"/getting-started-videos/","best practice videos",{"text":230,"config":231},"Integrations",{"href":232,"dataGaName":233,"dataGaLocation":48},"/integrations/","integrations",{"title":235,"items":236},"Discover",[237,242,247,252],{"text":238,"config":239},"Customer success stories",{"href":240,"dataGaName":241,"dataGaLocation":48},"/customers/","customer success stories",{"text":243,"config":244},"Blog",{"href":245,"dataGaName":246,"dataGaLocation":48},"/blog/","blog",{"text":248,"config":249},"The Source",{"href":250,"dataGaName":251,"dataGaLocation":48},"/the-source/","the source",{"text":253,"config":254},"Remote",{"href":255,"dataGaName":256,"dataGaLocation":48},"https://handbook.gitlab.com/handbook/company/culture/all-remote/","remote",{"title":258,"items":259},"Connect",[260,265,270,275,280],{"text":261,"config":262},"GitLab Services",{"href":263,"dataGaName":264,"dataGaLocation":48},"/services/","services",{"text":266,"config":267},"Community",{"href":268,"dataGaName":269,"dataGaLocation":48},"/community/","community",{"text":271,"config":272},"Forum",{"href":273,"dataGaName":274,"dataGaLocation":48},"https://forum.gitlab.com/","forum",{"text":276,"config":277},"Events",{"href":278,"dataGaName":279,"dataGaLocation":48},"/events/","events",{"text":281,"config":282},"Partners",{"href":283,"dataGaName":284,"dataGaLocation":48},"/partners/","partners",{"textColor":286,"title":287,"text":288,"link":289},"#000","What’s new in GitLab","Stay updated with our latest features and improvements.",{"text":290,"config":291},"Read the latest",{"href":292,"dataGaName":293,"dataGaLocation":48},"/releases/whats-new/","whats new",{"text":295,"config":296,"lists":298},"Company",{"dataNavLevelOne":297},"company",[299],{"items":300},[301,306,312,314,319,324,329,334,339,344,349],{"text":302,"config":303},"About",{"href":304,"dataGaName":305,"dataGaLocation":48},"/company/","about",{"text":307,"config":308,"footerGa":311},"Jobs",{"href":309,"dataGaName":310,"dataGaLocation":48},"/jobs/","jobs",{"dataGaName":310},{"text":276,"config":313},{"href":278,"dataGaName":279,"dataGaLocation":48},{"text":315,"config":316},"Leadership",{"href":317,"dataGaName":318,"dataGaLocation":48},"/company/team/e-group/","leadership",{"text":320,"config":321},"Team",{"href":322,"dataGaName":323,"dataGaLocation":48},"/company/team/","team",{"text":325,"config":326},"Handbook",{"href":327,"dataGaName":328,"dataGaLocation":48},"https://handbook.gitlab.com/","handbook",{"text":330,"config":331},"Investor relations",{"href":332,"dataGaName":333,"dataGaLocation":48},"https://ir.gitlab.com/","investor relations",{"text":335,"config":336},"Trust Center",{"href":337,"dataGaName":338,"dataGaLocation":48},"/security/","trust center",{"text":340,"config":341},"AI Transparency Center",{"href":342,"dataGaName":343,"dataGaLocation":48},"/ai-transparency-center/","ai transparency center",{"text":345,"config":346},"Newsletter",{"href":347,"dataGaName":348,"dataGaLocation":48},"/company/contact/#contact-forms","newsletter",{"text":350,"config":351},"Press",{"href":352,"dataGaName":353,"dataGaLocation":48},"/press/","press",{"text":355,"config":356,"lists":357},"Contact us",{"dataNavLevelOne":297},[358],{"items":359},[360,363,368],{"text":55,"config":361},{"href":57,"dataGaName":362,"dataGaLocation":48},"talk to sales",{"text":364,"config":365},"Support portal",{"href":366,"dataGaName":367,"dataGaLocation":48},"https://support.gitlab.com","support portal",{"text":369,"config":370},"Customer portal",{"href":371,"dataGaName":372,"dataGaLocation":48},"https://customers.gitlab.com/customers/sign_in/","customer portal",{"close":374,"login":375,"suggestions":382},"Close",{"text":376,"link":377},"To search repositories and projects, login to",{"text":378,"config":379},"gitlab.com",{"href":62,"dataGaName":380,"dataGaLocation":381},"search login","search",{"text":383,"default":384},"Suggestions",[385,387,391,393,397,401],{"text":77,"config":386},{"href":82,"dataGaName":77,"dataGaLocation":381},{"text":388,"config":389},"Code Suggestions (AI)",{"href":390,"dataGaName":388,"dataGaLocation":381},"/solutions/code-suggestions/",{"text":111,"config":392},{"href":113,"dataGaName":111,"dataGaLocation":381},{"text":394,"config":395},"GitLab on AWS",{"href":396,"dataGaName":394,"dataGaLocation":381},"/partners/technology-partners/aws/",{"text":398,"config":399},"GitLab on Google Cloud",{"href":400,"dataGaName":398,"dataGaLocation":381},"/partners/technology-partners/google-cloud-platform/",{"text":402,"config":403},"Why GitLab?",{"href":90,"dataGaName":402,"dataGaLocation":381},{"freeTrial":405,"mobileIcon":410,"desktopIcon":415,"secondaryButton":418},{"text":406,"config":407},"Start free trial",{"href":408,"dataGaName":53,"dataGaLocation":409},"https://gitlab.com/-/trials/new/","nav",{"altText":411,"config":412},"Gitlab Icon",{"src":413,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203874/jypbw1jx72aexsoohd7x.svg","gitlab icon",{"altText":411,"config":416},{"src":417,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1758203875/gs4c8p8opsgvflgkswz9.svg",{"text":419,"config":420},"Get Started",{"href":421,"dataGaName":422,"dataGaLocation":409},"https://gitlab.com/-/trial_registrations/new?glm_source=about.gitlab.com/get-started/","get started",{"freeTrial":424,"mobileIcon":428,"desktopIcon":430},{"text":425,"config":426},"Learn more about GitLab Duo",{"href":82,"dataGaName":427,"dataGaLocation":409},"gitlab duo",{"altText":411,"config":429},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":431},{"src":417,"dataGaName":414,"dataGaLocation":409},{"button":433,"mobileIcon":438,"desktopIcon":440},{"text":434,"config":435},"/switch",{"href":436,"dataGaName":437,"dataGaLocation":409},"#contact","switch",{"altText":411,"config":439},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":441},{"src":442,"dataGaName":414,"dataGaLocation":409},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1773335277/ohhpiuoxoldryzrnhfrh.png",{"freeTrial":444,"mobileIcon":449,"desktopIcon":451},{"text":445,"config":446},"Back to pricing",{"href":190,"dataGaName":447,"dataGaLocation":409,"icon":448},"back to pricing","GoBack",{"altText":411,"config":450},{"src":413,"dataGaName":414,"dataGaLocation":409},{"altText":411,"config":452},{"src":417,"dataGaName":414,"dataGaLocation":409},{"title":454,"button":455,"config":460},"See how agentic AI transforms software delivery",{"text":456,"config":457},"Watch GitLab Transcend now",{"href":458,"dataGaName":459,"dataGaLocation":48},"/events/transcend/virtual/","transcend event",{"layout":461,"icon":462,"disabled":29},"release","AiStar",{"data":464},{"text":465,"source":466,"edit":472,"contribute":477,"config":482,"items":487,"minimal":692},"Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license",{"text":467,"config":468},"View page source",{"href":469,"dataGaName":470,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/","page source","footer",{"text":473,"config":474},"Edit this page",{"href":475,"dataGaName":476,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/content/","web ide",{"text":478,"config":479},"Please contribute",{"href":480,"dataGaName":481,"dataGaLocation":471},"https://gitlab.com/gitlab-com/marketing/digital-experience/about-gitlab-com/-/blob/main/CONTRIBUTING.md/","please contribute",{"twitter":483,"facebook":484,"youtube":485,"linkedin":486},"https://twitter.com/gitlab","https://www.facebook.com/gitlab","https://www.youtube.com/channel/UCnMGQ8QHMAnVIsI3xJrihhg","https://www.linkedin.com/company/gitlab-com",[488,535,587,631,658],{"title":188,"links":489,"subMenu":504},[490,494,499],{"text":491,"config":492},"View plans",{"href":190,"dataGaName":493,"dataGaLocation":471},"view plans",{"text":495,"config":496},"Why Premium?",{"href":497,"dataGaName":498,"dataGaLocation":471},"/pricing/premium/","why premium",{"text":500,"config":501},"Why Ultimate?",{"href":502,"dataGaName":503,"dataGaLocation":471},"/pricing/ultimate/","why ultimate",[505],{"title":506,"links":507},"Contact Us",[508,511,513,515,520,525,530],{"text":509,"config":510},"Contact sales",{"href":57,"dataGaName":58,"dataGaLocation":471},{"text":364,"config":512},{"href":366,"dataGaName":367,"dataGaLocation":471},{"text":369,"config":514},{"href":371,"dataGaName":372,"dataGaLocation":471},{"text":516,"config":517},"Status",{"href":518,"dataGaName":519,"dataGaLocation":471},"https://status.gitlab.com/","status",{"text":521,"config":522},"Terms of use",{"href":523,"dataGaName":524,"dataGaLocation":471},"/terms/","terms of use",{"text":526,"config":527},"Privacy statement",{"href":528,"dataGaName":529,"dataGaLocation":471},"/privacy/","privacy statement",{"text":531,"config":532},"Cookie preferences",{"dataGaName":533,"dataGaLocation":471,"id":534,"isOneTrustButton":29},"cookie preferences","ot-sdk-btn",{"title":93,"links":536,"subMenu":545},[537,541],{"text":538,"config":539},"DevSecOps platform",{"href":75,"dataGaName":540,"dataGaLocation":471},"devsecops platform",{"text":542,"config":543},"AI-Assisted Development",{"href":82,"dataGaName":544,"dataGaLocation":471},"ai-assisted development",[546],{"title":547,"links":548},"Topics",[549,554,559,564,569,572,577,582],{"text":550,"config":551},"CICD",{"href":552,"dataGaName":553,"dataGaLocation":471},"/topics/ci-cd/","cicd",{"text":555,"config":556},"GitOps",{"href":557,"dataGaName":558,"dataGaLocation":471},"/topics/gitops/","gitops",{"text":560,"config":561},"DevOps",{"href":562,"dataGaName":563,"dataGaLocation":471},"/topics/devops/","devops",{"text":565,"config":566},"Version Control",{"href":567,"dataGaName":568,"dataGaLocation":471},"/topics/version-control/","version control",{"text":23,"config":570},{"href":571,"dataGaName":11,"dataGaLocation":471},"/topics/devsecops/",{"text":573,"config":574},"Cloud Native",{"href":575,"dataGaName":576,"dataGaLocation":471},"/topics/cloud-native/","cloud native",{"text":578,"config":579},"AI for Coding",{"href":580,"dataGaName":581,"dataGaLocation":471},"/topics/devops/ai-for-coding/","ai for coding",{"text":583,"config":584},"Agentic AI",{"href":585,"dataGaName":586,"dataGaLocation":471},"/topics/agentic-ai/","agentic ai",{"title":588,"links":589},"Solutions",[590,592,594,599,603,606,610,613,615,618,621,626],{"text":135,"config":591},{"href":130,"dataGaName":135,"dataGaLocation":471},{"text":124,"config":593},{"href":107,"dataGaName":108,"dataGaLocation":471},{"text":595,"config":596},"Agile development",{"href":597,"dataGaName":598,"dataGaLocation":471},"/solutions/agile-delivery/","agile delivery",{"text":600,"config":601},"SCM",{"href":120,"dataGaName":602,"dataGaLocation":471},"source code management",{"text":550,"config":604},{"href":113,"dataGaName":605,"dataGaLocation":471},"continuous integration & delivery",{"text":607,"config":608},"Value stream management",{"href":163,"dataGaName":609,"dataGaLocation":471},"value stream management",{"text":555,"config":611},{"href":612,"dataGaName":558,"dataGaLocation":471},"/solutions/gitops/",{"text":173,"config":614},{"href":175,"dataGaName":176,"dataGaLocation":471},{"text":616,"config":617},"Small business",{"href":180,"dataGaName":181,"dataGaLocation":471},{"text":619,"config":620},"Public sector",{"href":185,"dataGaName":186,"dataGaLocation":471},{"text":622,"config":623},"Education",{"href":624,"dataGaName":625,"dataGaLocation":471},"/solutions/education/","education",{"text":627,"config":628},"Financial services",{"href":629,"dataGaName":630,"dataGaLocation":471},"/solutions/finance/","financial services",{"title":193,"links":632},[633,635,637,639,642,644,646,648,650,652,654,656],{"text":205,"config":634},{"href":207,"dataGaName":208,"dataGaLocation":471},{"text":210,"config":636},{"href":212,"dataGaName":213,"dataGaLocation":471},{"text":215,"config":638},{"href":217,"dataGaName":218,"dataGaLocation":471},{"text":220,"config":640},{"href":222,"dataGaName":641,"dataGaLocation":471},"docs",{"text":243,"config":643},{"href":245,"dataGaName":246,"dataGaLocation":471},{"text":238,"config":645},{"href":240,"dataGaName":241,"dataGaLocation":471},{"text":253,"config":647},{"href":255,"dataGaName":256,"dataGaLocation":471},{"text":261,"config":649},{"href":263,"dataGaName":264,"dataGaLocation":471},{"text":266,"config":651},{"href":268,"dataGaName":269,"dataGaLocation":471},{"text":271,"config":653},{"href":273,"dataGaName":274,"dataGaLocation":471},{"text":276,"config":655},{"href":278,"dataGaName":279,"dataGaLocation":471},{"text":281,"config":657},{"href":283,"dataGaName":284,"dataGaLocation":471},{"title":295,"links":659},[660,662,664,666,668,670,672,676,681,683,685,687],{"text":302,"config":661},{"href":304,"dataGaName":297,"dataGaLocation":471},{"text":307,"config":663},{"href":309,"dataGaName":310,"dataGaLocation":471},{"text":315,"config":665},{"href":317,"dataGaName":318,"dataGaLocation":471},{"text":320,"config":667},{"href":322,"dataGaName":323,"dataGaLocation":471},{"text":325,"config":669},{"href":327,"dataGaName":328,"dataGaLocation":471},{"text":330,"config":671},{"href":332,"dataGaName":333,"dataGaLocation":471},{"text":673,"config":674},"Sustainability",{"href":675,"dataGaName":673,"dataGaLocation":471},"/sustainability/",{"text":677,"config":678},"Diversity, inclusion and belonging (DIB)",{"href":679,"dataGaName":680,"dataGaLocation":471},"/diversity-inclusion-belonging/","Diversity, inclusion and belonging",{"text":335,"config":682},{"href":337,"dataGaName":338,"dataGaLocation":471},{"text":345,"config":684},{"href":347,"dataGaName":348,"dataGaLocation":471},{"text":350,"config":686},{"href":352,"dataGaName":353,"dataGaLocation":471},{"text":688,"config":689},"Modern Slavery Transparency Statement",{"href":690,"dataGaName":691,"dataGaLocation":471},"https://handbook.gitlab.com/handbook/legal/modern-slavery-act-transparency-statement/","modern slavery transparency statement",{"items":693},[694,697,700],{"text":695,"config":696},"Terms",{"href":523,"dataGaName":524,"dataGaLocation":471},{"text":698,"config":699},"Cookies",{"dataGaName":533,"dataGaLocation":471,"id":534,"isOneTrustButton":29},{"text":701,"config":702},"Privacy",{"href":528,"dataGaName":529,"dataGaLocation":471},[704],{"id":705,"title":9,"body":27,"config":706,"content":708,"description":27,"extension":26,"meta":712,"navigation":29,"path":713,"seo":714,"stem":715,"__hash__":716},"blogAuthors/en-us/blog/authors/dov-hershkovitch.yml",{"template":707},"BlogAuthor",{"name":9,"config":709},{"headshot":710,"ctfId":711},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1749665628/Blog/Author%20Headshots/dhershkovitch-headshot.png","dhershkovitch",{},"/en-us/blog/authors/dov-hershkovitch",{},"en-us/blog/authors/dov-hershkovitch","Iz4JuWpp9w9MyL2i-FC6CmJS1rnfmg76IL873W1AcMU",[718,731,746],{"content":719,"config":729},{"title":720,"description":721,"authors":722,"heroImage":724,"date":725,"body":726,"category":11,"tags":727},"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",[723],"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/).",[625,728],"open source",{"featured":14,"template":15,"slug":730},"teaching-software-development-the-easy-way-using-gitlab",{"content":732,"config":744},{"description":733,"authors":734,"heroImage":736,"date":737,"title":738,"body":739,"category":11,"tags":740},"AI-generated code is 34% of development work. Discover how to balance productivity gains with quality, reliability, and security.",[735],"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.",[741,742,743],"AI/ML","DevOps platform","security",{"featured":29,"template":15,"slug":745},"ai-is-reshaping-devsecops-attend-gitlab-transcend-to-see-whats-next",{"content":747,"config":758},{"title":748,"description":749,"authors":750,"heroImage":752,"date":753,"body":754,"category":11,"tags":755},"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.",[751],"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.",[576,23,756,757],"product","features",{"featured":29,"template":15,"slug":759},"atlassian-ending-data-center-as-gitlab-maintains-deployment-choice",{"promotions":761},[762,776,787,798],{"id":763,"categories":764,"header":766,"text":767,"button":768,"image":773},"ai-modernization",[765],"ai-ml","Is AI achieving its promise at scale?","Quiz will take 5 minutes or less",{"text":769,"config":770},"Get your AI maturity score",{"href":771,"dataGaName":772,"dataGaLocation":246},"/assessments/ai-modernization-assessment/","modernization assessment",{"config":774},{"src":775},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/qix0m7kwnd8x2fh1zq49.png",{"id":777,"categories":778,"header":779,"text":767,"button":780,"image":784},"devops-modernization",[756,11],"Are you just managing tools or shipping innovation?",{"text":781,"config":782},"Get your DevOps maturity score",{"href":783,"dataGaName":772,"dataGaLocation":246},"/assessments/devops-modernization-assessment/",{"config":785},{"src":786},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138785/eg818fmakweyuznttgid.png",{"id":788,"categories":789,"header":790,"text":767,"button":791,"image":795},"security-modernization",[743],"Are you trading speed for security?",{"text":792,"config":793},"Get your security maturity score",{"href":794,"dataGaName":772,"dataGaLocation":246},"/assessments/security-modernization-assessment/",{"config":796},{"src":797},"https://res.cloudinary.com/about-gitlab-com/image/upload/v1772138786/p4pbqd9nnjejg5ds6mdk.png",{"id":799,"paths":800,"header":803,"text":804,"button":805,"image":810},"github-azure-migration",[801,802],"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":806,"config":807},"See how GitLab compares to GitHub",{"href":808,"dataGaName":809,"dataGaLocation":246},"/compare/gitlab-vs-github/github-azure-migration/","github azure migration",{"config":811},{"src":786},{"header":813,"blurb":814,"button":815,"secondaryButton":820},"Start building faster today","See what your team can do with the intelligent orchestration platform for DevSecOps.\n",{"text":816,"config":817},"Get your free trial",{"href":818,"dataGaName":53,"dataGaLocation":819},"https://gitlab.com/-/trial_registrations/new?glm_content=default-saas-trial&glm_source=about.gitlab.com/","feature",{"text":509,"config":821},{"href":57,"dataGaName":58,"dataGaLocation":819},1777493607772]