Closed
Bug 1455697
Opened 7 years ago
Closed 7 years ago
Provide taskId as context when firing a hook
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
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!
Assignee | ||
Comment 1•7 years ago
|
||
Comment 2•7 years ago
|
||
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
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Hooks → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•