Closed
Bug 1490051
Opened 7 years ago
Closed 7 years ago
Cleanup funsize workers.
Categories
(Release Engineering :: Release Automation, enhancement)
Release Engineering
Release Automation
Tracking
(firefox-esr60 fixed)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| firefox-esr60 | --- | fixed |
People
(Reporter: tomprince, Assigned: tomprince)
References
Details
Attachments
(2 files)
There is unused code to repackage partials (we generate them in the new format directly, now) and pass data to the tasks indirectly through `extra`.
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Comment on attachment 9007833 [details]
Bug 1490051: Remove unused partial recompression support; r?sfraser
Simon Fraser [:sfraser] ⌚️GMT has approved the revision.
Attachment #9007833 -
Flags: review+
| Assignee | ||
Updated•7 years ago
|
Keywords: leave-open
Pushed by mozilla@hocat.ca:
https://hg.mozilla.org/integration/autoland/rev/34ef3514a7e6
Remove unused partial recompression support; r=sfraser
Comment 5•7 years ago
|
||
| bugherder | ||
Updated•7 years ago
|
Attachment #9007834 -
Attachment description: Bug 1490051: Pass partial configuration to funsize explicitly, rather than smuggling through the task `extra`s; r=sfraser → Bug 1490051: Pass partial configuration to funsize explicitly, rather than smuggling through the task `extra`s; r?sfraser
Comment 6•7 years ago
|
||
We've a discussion going on about how we should pass in task configuration. The current setup is a json blob, about 40 lines / 1900 characters, and is passed in through 'extra'.
The options seem to be:
1. Use `extra` in the task definition
2. Encode a json blob into a string, in an environment variable
3. Ask for a schema change to the worker's payload.
Which of these is preferred? Are there other options we've missed?
Flags: needinfo?(dustin)
Comment 7•7 years ago
|
||
Yeah, I chatted with Tom briefly, and he pointed out that #2 isn't very readable, since it's JSON-in-JSON. #3 is sort of off the table as far as docker-worker is concerned, but for generic-worker, maybe we could propose that `env` values can be arbitrary objects that are JSON-serialized into OS environment variables? At any rate, moving to g-w for this is probably not worth it.
Given that "don't use task.extra to send data to the task" is a mild preference, and that readability is important, and that the existing code implements #1, it seems to me like a tie between #1 and #2. Doing both seems worse than doing either one.
Flags: needinfo?(dustin)
Comment 8•7 years ago
|
||
Thanks! For me, I'd be happy to move away from `extra` if there was an option that kept the readability. I'd vote for #1, as #2 also means we need to modify the release templates used in ship-it
Comment 9•7 years ago
|
||
#1's good, let's do it (and I think that means "no change", so easily done!)
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•7 years ago
|
Keywords: leave-open
| Assignee | ||
Comment 10•7 years ago
|
||
| bugherder uplift | ||
status-firefox-esr60:
--- → fixed
Updated•1 year ago
|
Component: Release Automation: Updates → Release Automation
You need to log in
before you can comment on or make changes to this bug.
Description
•