Because we migrated to github actions.
ooh ok.. I found them now...
only problem is the file name does not include the version build number...
PCSX2 (v1.7.0-r672)(Dev)(vs2019)(Orphis)_Win32.7z
.......................^
...................this above
the revision number included at Orphis build bot is missing from the GitHub Actions (artifact file names)
so I don't know which to re-label the file name to ...
Yeah but is there some specific reason you need them? I don't really recommend using the CI artifacts.
I need the revision numbers to keep track of the builds in order they come and for referencing the build if there is a
bug I need to report...
why not use them how else am I gonna get up to date builds for 64bit since Orphis build bot only does 32bit?
(12-10-2020, 02:00 AM)Melchior Wrote: [ -> ]I need the revision numbers to keep track of the builds in order they come and for referencing the build if there is a
bug I need to report...
Well if you don't know how to do that then you probably shouldn't be doing it.
Our CI artifacts are not for end-user consumption. They're for internal use.
(12-10-2020, 02:00 AM)Melchior Wrote: [ -> ]why not use them how else am I gonna get up to date builds for 64bit since Orphis build bot only does 32bit?
Because I'm telling you I don't recommend you do that.
There's a reason the builds aren't on Orphis yet.