Closed Bug 1455697 Opened 3 years ago Closed 3 years ago
Id as context when firing a hook
The hook spec includes the create task's taskId in the JSON-e context. Currently Hooks does not provide that value -- but the value exists at the time the JSON-e render method is called. So we could easily add it!
Commits pushed to master at https://github.com/taskcluster/taskcluster-hooks https://github.com/taskcluster/taskcluster-hooks/commit/5770ba4dc542dd5352b59ba110c0d85d44ecd4af Bug 1455697 - fix tests to run when secrets are here https://github.com/taskcluster/taskcluster-hooks/commit/09eb08491a54fad35e86b28ecf0cd6fe11517e6f Bug 1455697 - provide newTaskId in context, too https://github.com/taskcluster/taskcluster-hooks/commit/3a802c14c3f7c7ca1317cf27cb715eda07907779 Bug 1455697 - rename newTaskId to taskId, document taskGroupId = taskId https://github.com/taskcluster/taskcluster-hooks/commit/8bce0c54222d18551b8911c4f6e27fccae045720 Merge pull request #96 from djmitche/bug1455697 Bug 1455697 - provide newTaskId in context, too
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.