Fix cron cleanup job on dev-stage01

RESOLVED FIXED

Status

P4
normal
RESOLVED FIXED
7 years ago
7 months ago

People

(Reporter: nthomas, Unassigned)

Tracking

Details

(Whiteboard: [cleanup][buildduty])

(Reporter)

Description

7 years ago
We're looking in /builds/opt/aus2/build, which is the old place, rather than /builds/opt/aus2/incoming/2/
Component: Release Engineering → Release Engineering: Machine Management
QA Contact: release → armenzg
Whiteboard: [cleanup]

Updated

7 years ago
Whiteboard: [cleanup] → [cleanup][buildduty]
Priority: -- → P4
I updated the crontab files on mpt-production-puppet and forced a puppet sync. Cleanup jobs now look like this:
@hourly cd /builds/opt/aus2/incoming/2 && for file in `find . -name 'complete.txt' -type f -mtime -10`; do url=`grep ^http $file`; if [ "$url" != "" ]; then echo $file `curl -sI $url | grep ^HTTP` | grep HTTP.*404 || continue; rm $file; fi; done >> snippets_removed.log
@hourly cd /builds/opt/aus2/incoming/2 && for file in `find . -name 'complete.txt' -type f -mtime -10`; do url=`grep ^url=http $file | grep -o http.*`; if [ "$url" != "" ]; then echo $file `curl -sI $url | grep ^HTTP` | grep HTTP.*404 || continue; rm $file; fi; done >> snippets_removed.log
Assignee: nobody → bhearsum
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
I had to adjust where the cleanup log went too because of permissions problems. The logs are now in: /builds/opt/aus2/snippets_removed.log
Bah, cltbld doesn't have permission to clean up the snippets. This has gotten non-trivial, I don't have time to tackle it, so I backed out all of my changes.
Assignee: bhearsum → nobody
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 4

7 years ago
Pasted bhearsum's crontab entries from comment 1 into ffxbld@dev-stage01's crontab.

Comment 5

7 years ago
Also commented out cltbld's corresponding crontab entries.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering

Updated

7 months ago
Product: Release Engineering → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.