spring engine binaries and debug symbols as a github release
Moderator: Moderators
spring engine binaries and debug symbols as a github release
Can someone with the access upload binaries and debug symbols as a github release?
- Silentwings
- Posts: 3720
- Joined: 25 Oct 2008, 00:23
Re: Spring 105.0 released: maintenance release
+1 on releasing this and finally calling time on maintainance.
Re github release, I've never actually tested it but Github claims to block pushes with >100Mb content https://docs.github.com/en/free-pro-tea ... arge-files. The debug symbols are 150Mb for each OS release, so I think no!
Re github release, I've never actually tested it but Github claims to block pushes with >100Mb content https://docs.github.com/en/free-pro-tea ... arge-files. The debug symbols are 150Mb for each OS release, so I think no!
Re: Spring 105.0 released: maintenance release
It's regarding storing large files in the repo. Github releases have no such limitations. See: https://github.com/beyond-all-reason/sp ... 4-g321b911Silentwings wrote: ↑01 Jan 2021, 20:46 +1 on releasing this and finally calling time on maintainance.
Re github release, I've never actually tested it but Github claims to block pushes with >100Mb content https://docs.github.com/en/free-pro-tea ... arge-files. The debug symbols are 150Mb for each OS release, so I think no!
Re: spring engine binaries and debug symbols as a github release
(split topic)
the source code from https://github.com/beyond-all-reason/sp ... 21b911.zip doesn't contain the git submodules: this very likely makes it impossible to compile that source package. If i remember right, there have been several reports about this with older spring releases, thats one of the reasons why you don't easily find links to github.
the release checklist IMHO is way to long: https://github.com/spring/spring/blob/d ... cklist.txt
anything which makes it longer should be avoided. what does manual uploading the files to github improve?
the source code from https://github.com/beyond-all-reason/sp ... 21b911.zip doesn't contain the git submodules: this very likely makes it impossible to compile that source package. If i remember right, there have been several reports about this with older spring releases, thats one of the reasons why you don't easily find links to github.
can this zip files be removed? this answers your question i guess...Can someone with the access upload binaries and debug symbols as a github release?
the release checklist IMHO is way to long: https://github.com/spring/spring/blob/d ... cklist.txt
anything which makes it longer should be avoided. what does manual uploading the files to github improve?
Re: spring engine binaries and debug symbols as a github release
It's added by github automatically every time a release or pre-release is made. In any case I feel with DVCS like git storing sources in zip is redundant. Github does it on its own, I don't mind, but if I ever need to go back in time I'll do git checkout with submodules. If you still feel like storing sources with all submodules, they can be added as yet another release artifact.abma wrote: ↑01 Jan 2021, 22:11 the source code from https://github.com/beyond-all-reason/sp ... 21b911.zip doesn't contain the git submodules: this very likely makes it impossible to compile that source package.
If you mean zip files with source code, then no, you cannot. The rest can be added / removed by any user with access rights. Even by a github action worker, like in case of BAR branch.
It's a reliable URL, that will never get deleted unless you want so.
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Why not have a github action to upload builds to github?
This seems like the easiest solution? That way github can be referenced for downloading past engine builds. Maybe I'm overlooking a critical issue with doing it this way?