Open Bug 1950910 Opened 1 year ago Updated 1 year ago

Create action decisions and task groups with titles that say what release phase they correspond to

Categories

(Release Engineering :: Applications: Shipit, enhancement)

enhancement

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: gabriel, Assigned: gabriel)

References

Details

Attachments

(2 files)

It's difficult to keep Taskcluster tabs straight when monitoring/debugging releases because they all say "Action: Release Promotion"

ShipIt might be able to pass in more information via. the generated phase hooks.

Attachment #9468979 - Attachment description: GitHub Pull Request → GitHub Pull Request (shipit/pull/1626)

Backed out for breaking chain of trust.

scriptworker.exceptions.CoTError: 'scriptworker:parent H51FVvkuSoiyn4KowJllZQ: the runtime task doesn\'t match any rebuilt definition!\n["[(\'change\',\\n"\n "  \'metadata.name\',\\n"\n "  (\'Action: Release Promotion\', \'Action: Promote "\n "Thunderbird-136.0-build1\'))]"]'

We could allow this field to be set dynamically by taskcluster if we add the "metadata.name" key to this list of keys that are ignored by CoT: https://github.com/mozilla-releng/scriptworker/blob/main/src/scriptworker/cot/verify.py#L935

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: