Bugzilla

Yeah. That would work.

With a on-push action we can add tasks to the revision on central that produces the shippable binaries, [that is the builds that end up being uploaded to github](https://firefox-source-docs.mozilla.org/testing/geckodriver/Releasing.html#make-the-release), adhoc.

For the archival path I'd suggest:

archive.mozilla.org/pub/geckodriver/releases/*<version>*/*<linux-x86_64|linux-i686|linux-aarch64>*/geckodriver-v*<version>*-*<linux-x86_64|linux-i686|linux-aarch64>*.deb

The actions take in an input with a predefined schema, so we don't need two (they are pretty flexible.)
I think uploading to the archive and import into the apt repository could be done in succession and don't need to be separate steps.

I was browsing the tasks again, and iiuc, and just to restate it, what we need to do is:

1. Add a push action that can be triggered via firefox-ci/treeherder to add geckodriver release tasks to the revision we want to ship
2. That action adds tasks to the revision that
    a. Package `geckodriver.tar.gz` on `geckodriver-signing`  into .deb packages ie. `geckodriver.deb`
    b. Upload the `geckodriver.deb` packages to the FTP archive.
    c. Import the `geckodriver.deb` packages to the apt repository.

While we are at it we should add tasks that upload  the signed `geckodriver.tar.gz` build and the `CHECKSUMS` to the archive.
We could also upload the builds for the other platforms to the archive with minimal extra effort.

Yeah. That would work.

With a on-push action we can add tasks to the revision on central that produces the shippable binaries, [that is the builds that end up being uploaded to github](https://firefox-source-docs.mozilla.org/testing/geckodriver/Releasing.html#make-the-release), adhoc.

For the archival path I'd suggest:

archive.mozilla.org/pub/geckodriver/releases/*<version>*/*<linux-x86_64|linux-i686|linux-aarch64>*/geckodriver-v*<version>*-*<linux-x86_64|linux-i686|linux-aarch64>*.deb

The actions take in an input with a predefined schema, so we don't need two (they are pretty flexible.)
I think uploading to the archive and import into the apt repository could be done in succession and don't need to be separate steps.

I was browsing the tasks again, and iiuc, and just to restate it, what we need to do is:

1. Add a push action that can be triggered via firefox-ci/treeherder to add geckodriver release tasks to the revision we want to ship
2. That action adds tasks to the revision that
    a. Package `geckodriver.tar.gz` on `geckodriver-signing`  into .deb packages ie. `geckodriver.deb`
    b. Upload the `geckodriver.deb` packages to the FTP archive.
    c. Import the `geckodriver.deb` packages to the apt repository.

While we are at it we could add tasks that upload  the signed `geckodriver.tar.gz` build, the `.asc` file, and the `CHECKSUMS` to the archive.
We could also upload the builds for the other platforms to the archive. But maybe those are different issues.