With bug 1577110 fixed the next release of geckodriver could be fully done via the toolchain builds!

I don't think we can release directly from taskcluster, because I don't think we can have long-term artifacts on there. We'd probably need to upload to archive.mozilla.org.

glob: I don't know if you're the right person to ask about this, but after some recent relability issues with releasing geckodriver from GitHub, we're trying to scope out how much effort it would be to release based on Mozilla infrastructure. I think that would roughly involve uploading the artifacts we're building on TaskCluster to (presumably) archive.mozilla.org whenever we want to release (this is not coupled to Firefox release cycles), and having some URL that can reliably be used to get the latest release. Do you know yourself, or know who we should ask about this?

This looks more like a RelEng question, redirecting.

Sounds like you'll want to create a beetmover task (these are the tasks that move release blobs over to archive.mozilla.org). I believe you'll need a new set of credentials from SRE Services to push to whatever directory we choose. Someone on Releng would need to help get these credentials in place.

You'll also need to figure out when you want this task to run. E.g, you could have a VERSION.txt file and the task only runs when it's modified maybe? Or you could manually trigger it when needed. Edit: Aki reminded me we should use shipit to handle releases if possible.

Is there signing involved in the release process as well? If so then that's another set of credentials that'll be needed for the signing task.

@jgraham - did the info ahal provided get you what you needed?

(apologies for the extremely late reply and response to needinfo)

(In reply to Cyrus Bond from comment #7)

@jgraham - did the info ahal provided get you what you needed?

(apologies for the extremely late reply and response to needinfo)

Now we are late as well. One question ahead, are all the steps as mentioned by Andrew are still actual? Who from RelEng could help us in getting the necessary credentials and getting the Beetmover task implemented?

Johan, maybe you could help us figuring this out? Thanks a lot!

Hey :whimboo!

One question ahead, are all the steps as mentioned by Andrew are still actual?

Yes, this is still valid as of today.

Who from RelEng could help us in getting the necessary credentials [...]?

I'd recommend reaching out to the Purple SRE team first. Like :ahal said, they are the ones issuing these creds. We just put them in the right Taskcluster worker.

[...] and getting the Beetmover task implemented?

When do you need this by?

Hi Johan, and sorry for the delay in response.

(In reply to Johan Lorenzo [:jlorenzo] from comment #9)

One question ahead, are all the steps as mentioned by Andrew are still actual?

Yes, this is still valid as of today.

That's good to hear. Thanks for the confirmation.

Who from RelEng could help us in getting the necessary credentials [...]?

I'd recommend reaching out to the Purple SRE team first. Like :ahal said, they are the ones issuing these creds. We just put them in the right Taskcluster worker.

Thanks. I'll note this down so that we know what to do when we have the capacity to work on that bug.

[...] and getting the Beetmover task implemented?

When do you need this by?

As of now we do not have any pressure. I'm just trying to collect necessary information to get an idea how much work would be involved and if possible we could get some help with the creation of the necessary Beetmover tasks.

Also the whole release process is mostly manual. We would have to figure out which parts could be automated, even with some scripts that could be located in mozilla-central and would be helpful for the version bumps, audits, crate publishing, etc.

Given the low frequency of geckodriver releases this bug might still have a lower priority for some time.