Bugzilla

(In reply to Andrew Halberstadt [:ahal] from comment #4)
> I have a WIP branch going here:
> https://github.com/mozilla-mobile/fenix/compare/master...ahal:beetmover
> 
> (ignore the contents of `beetmover.py` and `beetmover/kind.yml` as they are mostly copied from `android-components`)
> 
> Hoping someone can verify that I'm on the right track.. In `android-components` it seems like artifacts are being copied to a maven destination? I'm assuming I'll need to replace this with a relative URL on `archive.m.o` and then somewhere in [here](https://github.com/mozilla-releng/scriptworker-scripts/tree/master/beetmoverscript/src/beetmoverscript) we'll translate that to a location on the server and handle auth and all that.

This is correct, we don't want to use maven logic, we want to use non-maven logic. We may be able to reuse some gecko logic here, e.g. https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/transforms/beetmover.py (there are a *lot* of [beetmover tasks and transforms in gecko](https://searchfox.org/mozilla-central/search?q=beetmover&path=) and we use declarative artifacts ([e.g.](https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/manifests/firefox_candidates.yml)) there; it may help to look at a [gecko release task](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Q0_3nD2-T-WuSgqnTuGylA) first.

> I guess for now I'll target `archive.m.o` until I hear otherwise.

+1

(In reply to Andrew Halberstadt [:ahal] from comment #4)
> I have a WIP branch going here:
> https://github.com/mozilla-mobile/fenix/compare/master...ahal:beetmover
> 
> (ignore the contents of `beetmover.py` and `beetmover/kind.yml` as they are mostly copied from `android-components`)
> 
> Hoping someone can verify that I'm on the right track.. In `android-components` it seems like artifacts are being copied to a maven destination? I'm assuming I'll need to replace this with a relative URL on `archive.m.o` and then somewhere in [here](https://github.com/mozilla-releng/scriptworker-scripts/tree/master/beetmoverscript/src/beetmoverscript) we'll translate that to a location on the server and handle auth and all that.

This is correct, we don't want to use maven logic, we want to use non-maven logic. We may be able to reuse some gecko logic here, e.g. https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/transforms/beetmover.py (there are a *lot* of [beetmover tasks and transforms in gecko](https://searchfox.org/mozilla-central/search?q=beetmover&path=) and we use declarative artifacts ([e.g.](https://searchfox.org/mozilla-central/source/taskcluster/taskgraph/manifests/firefox_candidates.yml)) there; it may help to look at a [gecko release task](https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Q0_3nD2-T-WuSgqnTuGylA) first.)

> I guess for now I'll target `archive.m.o` until I hear otherwise.

+1