browser_ui/4_verify/ci_variable/pipeline_with_protected_variable_spec.rb | Verify Pipeline with protected variable exposes variable on protected branch
Docs: https://docs.gitlab.com/ee/ci/variables/#protected-environment-variables
Related epic: gitlab-org&1669
Steps
- Via API:
- Create new project
- Spin up runner
- Commit CI file which echo out a CI protected variable which is defined later on in this test.
- Define user for developer role
- Define user for maintainer role
- Login to Gitlab
- Visit project
- Invite both users above to protect with their appropriate role
- Add protected variable via CI/CD settings (protected checkbox is marked by default)
- Create a protected branch via API
- Login as each user and make a commit to the protected branch to trigger a pipeline
- View each pipeline job log and verify protected variable value is displayed
- Login as each user and create a new merge request to master to trigger a pipeline
- View each pipeline job log and verify protected variable value is not displayed because these branches are non-protected.
- Remove runners afterward.
Title
browser_ui/4_verify/ci_variable/pipeline_with_protected_variable_spec.rb | Pipelines with protected variable
Full description
This is E2E test for when pipeline has a protected variable. The variable is only executable if the pipeline runs on a protected branch and not executable if the branch is non-protected (e.g a merge request). As default when create a protected branch via API, access is given to developer and maintainer; therefore, testing with these roles.
File path
qa/specs/features/browser_ui/4_verify/ci_variable/pipeline_with_protected_variable_spec.rb
Edited by GitLab QA Bot