Skip to content

Bring feature branch cleaning in line with Browserker

Craig Smith requested to merge update_how_feature_branch_images_are_cleaned_325013 into master

What does this MR do?

https://gitlab.com/gitlab-org/security-products/analyzers/browserker/-/merge_requests/202 moved feature branch image creating to the format:

registry.gitlab.com/gitlab-org/security-products/analyzers/browserker/BRANCH_NAME-SHA:current
registry.gitlab.com/gitlab-org/security-products/analyzers/browserker/BRANCH_NAME-SHA:future

https://gitlab.com/gitlab-org/security-products/analyzers/browserker/-/merge_requests/202#note_550206316 suggested that DAST and Browserker should be consistent.

This MR does the same thing to DAST, updating the format to

registry.gitlab.com/gitlab-org/security-products/analyzers/dast/BRANCH_NAME-SHA:current
registry.gitlab.com/gitlab-org/security-products/analyzers/dast/BRANCH_NAME-SHA:future

This will allow clean-registry.sh to remove tags and folders without the large cleanup task when merging to master.

What are the relevant issue numbers?

gitlab-org/gitlab#325013 (closed)

Does this MR meet the acceptance criteria?

Edited by Craig Smith

Merge request reports