Closed Bug 2073481 Opened 2 months ago Closed 1 month ago

update chain-of-trust verification to allow mix of git/hg tasks

Categories

(Release Engineering :: Release Automation, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jcristau, Unassigned)

References

Details

Bug 2064412 is a bit of a canary in that it's the first kind that's being switched to clone from git and goes through chain-of-trust. It's uncovered failures at least twice already, so filing this to track the fix(es) / discussion.

Among the checks that CoT does today:

  • each task's *_HEAD_REPOSITORY env var matches metadata.source (which failed last week and prompted bug 2071338), in get_source_url
  • sibling tasks (same decision_task_id) share metadata.source (which the change in bug 2071338 violates), in trace_back_to_tree

Suggestion:

  • revert bug 2071338, so all tasks go back to having the same repo in metadata.source
  • update get_source_url to ignore a mismatch if 1) no restricted scopes are used (useful for try, where the url mapping to a github repo is entirely untrusted), or 2) lando says the revisions are the same
Depends on: 2073542
Blocks: 2070444
Blocks: 2074022
Depends on: 2074494

This is now working, build-components tasks on central are cloning from Github

Status: NEW → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.