[tracking] add support for pushflatpakscript in scriptworkers
Categories
(Release Engineering :: Release Automation, task)
Tracking
(Not tracked)
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
Attachments
(8 files, 1 obsolete file)
63 bytes,
text/x-github-pull-request
|
Details | Review | |
55 bytes,
text/x-github-pull-request
|
Details | Review | |
63 bytes,
text/x-github-pull-request
|
Details | Review | |
60 bytes,
text/x-github-pull-request
|
Details | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
60 bytes,
text/x-github-pull-request
|
Details | Review | |
55 bytes,
text/x-github-pull-request
|
Details | Review | |
63 bytes,
text/x-github-pull-request
|
Details | Review |
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.
Assignee | ||
Comment 1•5 years ago
|
||
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 | ||
Comment 2•5 years ago
|
||
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 7•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 8•5 years ago
|
||
Assignee | ||
Comment 9•5 years ago
|
||
Assignee | ||
Comment 10•5 years ago
|
||
Comment 11•5 years ago
|
||
Hi,
Where can I track the release for this feature? And which versions of FF will this be launched for?
Assignee | ||
Comment 12•5 years ago
|
||
(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!
Assignee | ||
Comment 13•5 years ago
|
||
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.
Assignee | ||
Comment 14•5 years ago
|
||
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)
Assignee | ||
Comment 15•5 years ago
|
||
Latest staging release:
- version: firefox 76.0b28 build1
- release: https://treeherder.mozilla.org/#/jobs?repo=try&revision=718d612f8f0e1a3d608559635f3b8c70e1c5a0af
- promote phase: https://firefox-ci-tc.services.mozilla.com/tasks/groups/dd19LScyTaWj7c1JYnu2PQ
- push phase: https://firefox-ci-tc.services.mozilla.com/tasks/groups/Kda6Z2duQ8yYmtrGMM231g
Successful (staging) flatpak pushed to the beta
channel in Flathub - https://firefox-ci-tc.services.mozilla.com/tasks/IUcHKFGOTtO0qcaXIJExHw
Assignee | ||
Comment 16•5 years ago
|
||
Amended the App-id from in-tree, and triggered another staging release as follows:
- version: firefox 76.0b29 build2
- release: https://treeherder.mozilla.org/#/jobs?repo=try&revision=2513b4fe9c80b1682d7b691e0b8daeedaa3eb989
- promote phase: https://firefox-ci-tc.services.mozilla.com/tasks/groups/NoudF3EsTzimLweycMGcOA
- push phase: https://firefox-ci-tc.services.mozilla.com/tasks/groups/eLxrr8XKQjWJNJFDXoxyZQ
Successful (staging) flatpak pushed to the beta
channel in Flathub - https://firefox-ci-tc.services.mozilla.com/tasks/dtiWWIezR_SzHTWJtiqHmg
Assignee | ||
Comment 17•5 years ago
|
||
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/
Assignee | ||
Comment 18•5 years ago
|
||
For posterity:
In order to test the currently-shipped Firefox Flatpaks on the beta channel:
- depending on the distribution, opening https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref from browser should cause GNOME Software/KDE discover to ask if user wants to install it
- alternatively
flatpak install --user https://flathub.org/beta-repo/appstream/org.mozilla.firefox.flatpakref
Description
•