Skip to content

Tags: axboe/fio

Tags

fio-3.38

Toggle fio-3.38's commit message
fio v3.38

fio-3.37

Toggle fio-3.37's commit message
fio v3.37

fio-3.36

Toggle fio-3.36's commit message
fio v3.36

fio-3.35

Toggle fio-3.35's commit message
fio v3.35

fio-3.34

Toggle fio-3.34's commit message
fio v3.34

fio-3.33

Toggle fio-3.33's commit message
fio v3.33

fio-3.32

Toggle fio-3.32's commit message
fio v3.32

test-tag-2022-08-09-2

Toggle test-tag-2022-08-09-2's commit message
ci: drop master branch requirement for AppVeyor releases

Even if we tag a commit on the master branch AppVeyor won't upload the
installers as GitHub release artifacts.

https://ci.appveyor.com/project/axboe/fio/builds/44416420/job/t1elejqo2yk3r72b

So just drop the requirement for AppVeyor to only upload release
artifacts from the master branch.

This seems to get things working on my fork:

https://ci.appveyor.com/project/vincentkfu/fio/builds/44417490/job/e6xtrwc6xlccrn0j

It's good to have the flexibility to store installers from other
branches in any case.

Signed-off-by: Vincent Fu <[email protected]>

fio-3.31

Toggle fio-3.31's commit message
fio v3.31