Am 29.05.19 um 18:01 schrieb Chris AtLee:
> Could we address this by running the "repackage" tasks as required on Try,
> either as part of the initial push, or added after via treeherder's "Add
> New Jobs" feature
I wonder if we should give them a name that reflects their deliverable
"download and test this", more than it's purpose.
Or even just create a dummy task that doesn't do anything but echo the
artifact, under a human-readable task name?
> On Wed, 29 May 2019 at 11:57, Botond Ballo wrote:
>> On Wed, May 29, 2019 at 11:03 AM Justin Wood wrote:
>>> * In CI we only produce tarballs and repack based on tarballs.
>> One thing that may be worth keeping in mind, is that we sometimes ask
>> users to test Try builds. (For example, if a developer can't reproduce
>> a bug locally, they might ask the bug's reporter to try a speculative
>> fix pushed to Try, by downloading the relevant build artifact from
>> If the build artifact uses a compression format that's not supported
>> out of the box on the user's platform, that could introduce friction
>> into this process.
>> release-engineering mailing list