E2E opt-out of keeping latest artifact at Project level
E2E test for new feature Make "keep latest artifact" a project-level configuration. This option is selected by default and this scenario is already covered in locked_artifacts_spec.rb. This test case is to cover scenario when this option is not selected, expire_in policy should be honored (once expired, artifact cannot be browsed).
Steps
- Log into GitLab
- Create new project and setup runner
- Visit Project -> Go to Settings -> CI/CD -> Unselect "Keep latest artifacts from last successful jobs"
- Commit CI that will produce artifact that expires in 1 second via API
- Go to pipeline page, wait for pipeline to finish, visit it
- Go to job
- Verify artifact browse button is not available.
- Visit group, go to group's pipeline page
- Go to group's latest pipeline and it's job
- Verify project artifact is not present
Potentially, step 7 - 10 could be done via API check, need research
To be filled in after automation completed
Title: |
Description: