On 8/9/22 16:40, Jens Axboe wrote:
On 8/9/22 10:19 AM, Vincent Fu wrote:
-----Original Message-----
From: Vincent Fu [mailto:vincent.fu@xxxxxxxxxxx]
Sent: Tuesday, August 9, 2022 9:31 AM
To: Jens Axboe <axboe@xxxxxxxxx>; fio@xxxxxxxxxxxxxxx
Subject: RE: [PATCH 0/1] ci: upload tagged AppVeyor installers as GitHub
releases
-----Original Message-----
From: Jens Axboe [mailto:axboe@xxxxxxxxx]
Sent: Tuesday, August 9, 2022 9:10 AM
To: Vincent Fu <vincent.fu@xxxxxxxxxxx>; fio@xxxxxxxxxxxxxxx
Subject: Re: [PATCH 0/1] ci: upload tagged AppVeyor installers as
GitHub
releases
<snip>
I applied the patch and updated the key, and pushed a test tag. Let's
see if this works!
--
Jens Axboe
Jens, if you don't want to wait you can kill this build:
<snip>
And then this one should (fingers crossed) push installers to GitHub:
<snip>
Ok I had to make a small tweak but I think it is all working now:
https://github.com/axboe/fio/releases
I pushed a tag to git.kernel.dk which got automatically pushed to GitHub
which then triggered the AppVeyor build and eventually we ended up with
the release artifacts on GitHub.
Excellent! Let's get a release tagged then...
Ok I think it all worked.
For each release AppVeyor will do two builds, one for the commit and one
for the tag.
I only saw the first build, forgot about the second, and thought that
the integration failed. So I deleted the tag on GitHub and then
re-tagged it to manually trigger the release process. So AppVeyor did
two builds for the tag which did no harm except waste their resources.
I also deleted the test release artifacts on GitHub from earlier today
to clean things up.
Vincent
