Closed Bug 1275034 Opened 4 years ago Closed 4 years ago

create decision tasks with the assumption they use the big-graph scheduler

Categories

(Taskcluster :: Services, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dustin, Assigned: garndt)

References

Details

Attachments

(2 files, 1 obsolete file)

mozilla-taskcluster should, for tasks configured from .taskcluster.yml, provide a new TASK_GROUP_ID into which it has inserted the decision task, and skip using the scheduler at all.

The schedulerid for the new task should be designed appropriately, as well, so that we can limit access to retriggers, etc.  I think that should involve both the level and the project, e.g., `l-{{level}}-{{project}}`
I wouldn't be surprised if the scheduler ID also has a similar character limit as the other identifiers.
Yup, schedulerID is limited to 22 characters:
https://github.com/taskcluster/taskcluster-queue/blob/master/schemas/create-task-request.yml#L35

"level-1-mozilla-inbound" is 23 by itself.
Assignee: dustin → garndt
So if we want to have a unique scheduler ID, we need something <= 22 characters.  Any suggestions on naming? If we include project, mozilla-inbound is 15 characters alone so we're also imposing a limit to how long the project names can be so it can fit into a scheduler ID.
Maybe we should compromise and just include the level, and enough to disambiguate these schedulers from non-gecko schedulers?  Something like `gecko-level-N`?  Then we can assign the relevant scopes to the per-level groups.  We generally don't want to give scopes specific to a project anyway.
Component: Index → Integration
Attached file mozilla-taskcluster PR 85 (obsolete) —
I think this should schedule the tasks the way we've been wanting.  This should also allow the decision task to be passed arguments for creating additional tasks with the same scheduler and group id.

I attempted to look into m-t's testing situation to see about testing this ahead of time, and it's as to be expected, a mess.  I can still add tests but thought I would show you this before I enter PTO at the end of the week.
Attachment #8770801 - Flags: review?(dustin)
Comment on attachment 8770801 [details] [review]
mozilla-taskcluster PR 85

I'll try to land this soon
Attachment #8770801 - Flags: review?(dustin) → review+
Attachment #8770801 - Attachment is obsolete: true
I updated this a little based on our discussion of setting the taskGroupId.  I don't know if that needs to be documented somewhere?  At the very least, probably in .taskcluster.yml, for which I'll submit another patch.
Attachment #8772900 - Flags: review?(garndt)
Comment on attachment 8772904 [details]
Bug 1275034: add comment about taskGroupId = taskId;

https://reviewboard.mozilla.org/r/65598/#review65654
Attachment #8772904 - Flags: review?(garndt) → review+
Attachment #8772900 - Flags: review?(garndt) → review+
Pushed by dmitchell@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5406ddf4a856
add comment about taskGroupId = taskId; r=garndt
This has been landed and pushed to heroku
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Component: Integration → Services
You need to log in before you can comment on or make changes to this bug.