Localization of blog categories and URLs" WWW delete Job update
What is changing in this MR?
This MR adds blog exclusion to rsync command on WWW deployment exclude_flag=( -x '^.*blog[/\\]') to avoid `LOCALE_CODE/blog` files deletion. Related to gitlab-com/marketing/digital-experience/gitlab-blog!177 (merged)
related gitlab-com/marketing/digital-experience/gitlab-blog#153 (closed)
Testing Process:
To test LOCALE_CODE/blog repo files are not deleted on WWW, this MR was created using the same GCP_BUCKET as our Blog MR, and a blog path exception was added to ignore everything matching blog files with: -x '^.*blog[/\\]'.
After testing the scenarios below -d literal is removed and replaced back with the $delete_flag variable.
| Description | Commands | Exclude flag | Screenshot | Job Log |
|---|---|---|---|---|
Dry run delete job with no exclusions: All LOCALE_CODE/blog files marked for deletion |
with_backoff gsutil -h "Cache-Control:public, max-age=$cache_control_max_age" -m rsync -n -d -x '.*breaking-changes.xml|blog/.*' -z css,html,js,txt -c -r "$src" "$dest" |
-x '.*breaking-changes.xml|blog/.*' |
 |
www-delete-job-dry-run.txt |
Running delete job with `/blog` exclusion: No LOCALE_CODE/blog files are deleted or referenced |
with_backoff gsutil -h "Cache-Control:public, max-age=$cache_control_max_age" -m rsync -n -d -x '.*breaking-changes.xml|^.*blog[/\\]' -z css,html,js,txt -c -r "$src" "$dest" |
-x '.*breaking-changes.xml|^.*blog[/\\]' |
www-delete-job-with-exclusion-flag.txt |
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained bysection on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Dry run test for www delete job with blog paths exclusion
Closes #153 (closed)
Edited by Margareth Mañunga