Closed
Bug 1185542
Opened 10 years ago
Closed 10 years ago
vcs-sync isn't working
Categories
(Developer Services :: General, task)
Developer Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: RyanVM, Assigned: hwine)
Details
Attachments
(1 file)
|
932 bytes,
patch
|
hwine
:
review+
hwine
:
checked-in+
|
Details | Diff | Splinter Review |
Looks like git.mo hasn't seen any changes since Friday even though Github shows more recent commits. I'm closing Gaia and all trees fed by Bumper Bot.
fallout from cutover from scl3 -> aws
AWS has a different policy for purging files from /tmp than mozilla uses in scl3
Assignee: nobody → hwine
Status: NEW → ASSIGNED
processes back working ~0920 PT, trees left closed until backlog burns down
|
Reporter | |
Comment 3•10 years ago
|
||
Everything's caught up and tests are green. Reopened!
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Interim solution (this is a legacy system on the way to decom):
- tweak start_ssh_agent to update (touch) time stamp
- add cron job to invoke the setups appropriately
This patch covers the first. The cronjob is added in another repo
https://hg.mozilla.org/users/hwine_mozilla.com/repo-sync-tools/rev/e54b59a255d4
Attachment #8636702 -
Flags: review+
Attachment #8636702 -
Flags: checked-in+
crontab portion checked in:
https://github.com/mozilla/build-vcs2aws/commit/3c5471b9ed311583793bd8f99cccec164950b35d
You need to log in
before you can comment on or make changes to this bug.
Description
•