Step Four: Site repo configuration

The following configuration steps are to be completed inside your site source code repository in GitLab.

1. Set your site's CI/CD configuration file to the value of your chosen package type in Step Two. This option is under Settings→CI/CD→General pipelines
2. Set your site's CI/CD variables. Settings→CI/CD→Variables
   • Add the variable(s) for the deployment process from Step Three.
3. Due to how pipelines are configured on code.il2, pipelines will only run on protected branches and tags. This means that you have to set tags and/or branches in your repo (depending on the options chosen in Step Three) to be protected for pipelines to actually run.
   • Protecting Tags:
     • Go to Settings→Repository→Protected Tags
     • Add a wildcard tag v* and select the users/groups allowed to create tags that match this pattern. The users/groups are completely up to you and how you want to limit who can deploy to staging/production.
   • Protecting Branches:
     • Go to Settings→Repository→Protected Branches
     • The master branch is protected by default. If you have set a custom PADAWAN_DEPLOYMENT_BRANCH then you must also set this branch to be protected. The users/groups are completely up to you and how you want to limit who can merge into this branch.

TIP

Visit Gitlab CI/CD Configuration Options for additional repository configuration tips and best practices.

TIP

Visit Pipeline Variables to view all the advanced configuration options that the Padawan pipeline provides.