Closed Bug 1617612 Opened 5 years ago Closed 5 years ago

[tracking] add support for pushflatpakscript in scriptworkers

Categories

(Release Engineering :: Release Automation, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mtabara, Assigned: mtabara)

References

Details

Attachments

(8 files, 1 obsolete file)

We're able to manually talk to the Flathub API. Now we need to automate this in a scriptworker. This bug is tracking all the work to make it up-to-date.

Used the code from bug 1591387 to trigger yet another try staging release as the old one had expired its artifacts.
Try staging release: here
Flatpak tar gz (based on 74.0b7): here

Assignee: nobody → mtabara
Assignee: mtabara → nobody
Assignee: nobody → mtabara
Status: NEW → ASSIGNED
Attachment #9129809 - Attachment is obsolete: true

Hi,

Where can I track the release for this feature? And which versions of FF will this be launched for?

(In reply to ritika from comment #11)

Hi,

Where can I track the release for this feature? And which versions of FF will this be launched for?

Hi! Still to be determined, we're currently streamlining the automation for this. Whenever we have the details for the first FF to officially ship this, I'll share them in the bug too. Thank you!

Latest try staging release I'm testing against is https://firefox-ci-tc.services.mozilla.com/tasks/groups/dd19LScyTaWj7c1JYnu2PQ. Once that's build, I'll schedule the push phase and hopefully see the push task green. I fixed the last remaining issues locally so I expect it to work smoothly.

Note to self, for posterity, the original script we used for publishing was:

#!/bin/bash
set -xe

# prepare_publish
git clone https://github.com/flatpak/flat-manager.git
flat-manager/flat-manager-client create $RELEASES_SERVER_ADDRESS "${RELEASE_CHANNEL}" > publish_build.txt

# finish_publish
tar -xvf $FLATPAK_TARBALL
flat-manager/flat-manager-client push $(cat publish_build.txt) repo

flat-manager/flat-manager-client commit --wait $(cat publish_build.txt)
flat-manager/flat-manager-client publish --wait $(cat publish_build.txt)
flat-manager/flat-manager-client purge $(cat publish_build.txt)

Amended the App-id from in-tree, and triggered another staging release as follows:

Successful (staging) flatpak pushed to the beta channel in Flathub - https://firefox-ci-tc.services.mozilla.com/tasks/dtiWWIezR_SzHTWJtiqHmg

All the publishing bits have landed. We can close this as most of the follow-up work is related to flatpak itself, likely in bug 1591387 or in bug 1441922.

Shout-out to :rail with whom I paired up to take this over the finish line! \o/

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED

For posterity:

In order to test the currently-shipped Firefox Flatpaks on the beta channel:

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: