Bugzilla

Hmm, thanks, that makes sense. Sounds like this is less of of a "low hanging fruit" than I anticipated.

> I think the ideal solution would be for the mach try invocation to check this locally and either error out before pushing, or print a warning like "The following tasks will be skipped:". But no ones gotten around to implementing this.. I think there might even be a bug on file.

Hmm, that's fair, but it's still a bummer - ideally, all jobs that _can_ be artifact-mode'd would use artifacts, and those that need to opt out (such as Android Shippable) would opt out.

I don't think I can prioritize the significant chunk of work that would enable that, and I don't think that the alternative solutions' benefits are sufficiently worth the work to implement them today. I'm going to plonk this into the backlog.

### Workaround

Edit your `mozconfig` file and disable the `ac_add_options --enable-artifact-builds` line before pushing to `try`.

Hmm, thanks, that makes sense. Sounds like this is less of of a "low hanging fruit" than I anticipated.

> I think the ideal solution would be for the mach try invocation to check this locally and either error out before pushing, or print a warning like "The following tasks will be skipped:". But no ones gotten around to implementing this.. I think there might even be a bug on file.

That's fair, but it's still a bummer - ideally, all jobs that _can_ be artifact-mode'd would use artifacts, and those that need to opt out (such as Android Shippable) would opt out.

I don't think I can prioritize the significant chunk of work that would enable that, and I don't think that the alternative solutions' benefits are sufficiently worth the work to implement them today. I'm going to plonk this into the backlog.

### Workaround

Edit your `mozconfig` file and disable the `ac_add_options --enable-artifact-builds` line before pushing to `try`.