Migrate remaining miscellaneous hooks from AWS -> GCP
Categories
(Release Engineering :: Firefox-CI Administration, task)
Tracking
(Not tracked)
People
(Reporter: ahal, Assigned: ahal)
References
Details
(Keywords: leave-open)
Attachments
(5 files)
There are still several hooks defined in ci-config
that run in AWS, like the code-review / code-coverage bots.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
This also switches the "testing" hooks to use it.
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/f026d3316360 Create GCP pools for code-review / code-coverage bots, r=marco,releng-reviewers,jcristau
Assignee | ||
Comment 3•1 year ago
|
||
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/84a9832e70bd Add missing scope for new code-coverage GCP pool, r=releng-reviewers,jcristau
Assignee | ||
Comment 5•1 year ago
|
||
Looks like the hook is working, but the task itself is failing, e.g:
https://firefox-ci-tc.services.mozilla.com/tasks/EEzX2LnrS4SIhhIbZOmeww
That doesn't immediately look like a GCP problem, but it was passing consistently prior to the switch. Maybe we need to update DNS in order to resolve api.coverage.testing.moz.tools
? Marco, what do you think?
Comment 6•1 year ago
|
||
It looks like the task is actually able to resolve the URL, but the server is returning 404 for this revision (https://api.coverage.testing.moz.tools/v2/path?repository=mozilla-central&changeset=616a6f1689dc99810e5d7e6465b781a49b6430c8&platform=all&suite=all doesn't work, while the non-testing https://api.testing.moz.tools/v2/path?repository=mozilla-central&changeset=616a6f1689dc99810e5d7e6465b781a49b6430c8&platform=all&suite=all works).
Looking at https://api.coverage.testing.moz.tools/v2/history it looks like the coverage for this revision was not uploaded (616a6f1689dc99810e5d7e6465b781a49b6430c8 is missing).
Let's check the next run of the hook.
Assignee | ||
Comment 7•1 year ago
|
||
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/dd1e1eb93658 Revert code-coverage/review testing hooks back to AWS, r=marco
Assignee | ||
Comment 9•1 year ago
|
||
Looks like the testing hooks are still failing after reverting to AWS:
https://firefox-ci-tc.services.mozilla.com/tasks/BF2TNDKlToqpJtycdQKjYw
I wonder if the initial switch got them into some kind of bad state that we need to manually get them out of again? Marco, do you think we should try switching production to GCP? Or do you think the same thing will happen there?
Comment 10•1 year ago
|
||
It looks like the Redis testing instance was full, I tried to upgrade it to a larger instance, let's see if it starts working again.
If it starts working again, we can move testing to gcp again and see if it works.
Assignee | ||
Comment 11•1 year ago
|
||
Reverting these back to AWS did not resolve the failures, then Marco noticed
the DB was full. After clearing that out they started working again. Let's
see if they work on GCP now.
Comment 12•1 year ago
|
||
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/d131a217a425 Switch code-coverage/review testing hooks back to GCP, r=marco
Assignee | ||
Comment 13•1 year ago
|
||
Woo, here's a green gcp task:
https://firefox-ci-tc.services.mozilla.com/tasks/LTTfkApyTDWnRawZTvL0rA
I guess I was just massively unlucky that this hit right in-between me switching the hook over to GCP. I'll put up a patch to migrate the non-testing hooks as well.
Assignee | ||
Comment 14•1 year ago
|
||
Comment 15•1 year ago
|
||
Pushed by ahalberstadt@mozilla.com: https://hg.mozilla.org/ci/ci-configuration/rev/9432f1650479 Switch code-coverage/review production hooks to GCP, r=marco
Comment 16•1 year ago
|
||
Marco, do you know what the plan is for project-relman/bugzilla-dashboard-backend-* hooks?
Comment 17•1 year ago
|
||
We can drop those hooks, I filed bug 1816884.
Assignee | ||
Updated•1 year ago
|
Description
•