Topic: Table Automated Daily Builds in Download page

Forums » Widelands Development » Homepage » Table Automated Daily Builds in Download page
palino
Avatar
Topic Opener
Joined: 2022-12-19, 08:06 UTC+1.0
Posts: 23
OS: Windows 11
Version: master
Ranking
Pry about Widelands
 Posted at: 2025-11-08, 15:22 UTC+1.0

The Automated Daily Builds table has some not working links and is disarranged for me. I have proposal for update which includes also future additions from existing PRs. Which one do you like more, the verbose or the narrow version?
red lines after GH #6911
yellow lines after GH #6908
green line after CB #4902

Attachment: image/png
wl_build_table.png
Top Quote
kaputtnik
Avatar
Joined: 2013-02-18, 20:48 UTC+1.0
Posts: 2724
OS: Archlinux
Version: current master
Ranking
One Elder of Players
Location: Germany
Posted at: 2025-11-09, 10:58 UTC+1.0

palino wrote

The Automated Daily Builds table has some not working links and is disarranged for me. I have proposal for update which includes also future additions from existing PRs. Which one do you like more, the verbose or the narrow version?

I fear there are no people available to keep both of your suggestion up to date over years… All developers are busy and probably don't find time after fixing a crash to update the table accordingly. But maybe it's useful to create a link to the bug reports on Codeberg, (or/and GitHub) e.g. for windows or MacOs.

I think the table is mainly for non developers, for people who want, or are encouraged to use a development build, to test new features. So it should be easy to understand, e.g. sorting by OS is more important than sorting by architecture, imho.

Top Quote
palino
Avatar
Topic Opener
Joined: 2022-12-19, 08:06 UTC+1.0
Posts: 23
OS: Windows 11
Version: master
Ranking
Pry about Widelands
 Posted at: 2025-11-09, 18:53 UTC+1.0

kaputtnik wrote

palino wrote

The Automated Daily Builds table has some not working links and is disarranged for me. I have proposal for update which includes also future additions from existing PRs. Which one do you like more, the verbose or the narrow version?

I fear there are no people available to keep both of your suggestion up to date over years… All developers are busy and probably don't find time after fixing a crash to update the table accordingly. But maybe it's useful to create a link to the bug reports on Codeberg, (or/and GitHub) e.g. for windows or MacOs.

I meant something else in the Crash reports column - the ability of binary to generate reports after crash, to be sent to the bug report, see attachment.

I think the table is mainly for non developers, for people who want, or are encouraged to use a development build, to test new features. So it should be easy to understand, e.g. sorting by OS is more important than sorting by architecture, imho.

The Compiler and Crash reports columns can be moved after Download and Hash columns, they are not so relevant for users, or they can be eventually removed.

We can also provide just a link to latest tag, but the naming could be unclear for common users. E.g. msvc or mingw in the names of artifacts is clear for developers, but users may not know it is related to Windows.

Attachment: image/png
crash_report.png
Top Quote
hessenfarmer
Avatar
Joined: 2014-12-11, 23:16 UTC+1.0
Posts: 2883
Version: always the latest
Ranking
One Elder of Players
Location: Bavaria
Posted at: Yesterday 23:12 UTC+1.0

Thanks for picking this up (and probably maintain in the future), as this table is really a bit outdated.
I like the narrow one but it should be sorted by OS, architecture, build type and compiler.
The crash report column is not really necessary as it is not a criteria, to select the build.
For the windows arm we should probably list the installer rather then the binary, as otherwise you would need to install a wrong and not runnable version of the binary first and then the correct one just to have the data dir.

Edited: Yesterday 23:12 UTC+1.0
Top Quote