The logs show it was available at the usual time. I need to understand more about cache headers to send them correctly for our sites, so your browser doesn't fool you.

The only thing I can't understand though is why all systems hide the GMT. It's like we are in Medieval time and we think that it's midday in the whole universe.

Because our server reports the files were uploaded at 5:13. Theirs show the job was finished at 8:13. I'm guessing this means the job sent the files right because the minutes match. I'll see if I can find out.

The first one is probably not updating because the latter doesn't work. I doubt there are others publishing regular development builds. (There was none at all when I joined.) If there is, there is a question of whether it is legit and not some trojan factory.

According to one of the discussions on their forum (the one about version control, which I just happened to decide to look at), OpenTTD does not use the forum anymore for development related matters, but IRC.

Why do you need Jenkins, when you have a cross compile environment? Simutrans does not have any automated tests ...

I have set up a crosscompilation on mz tiny virtual server, and it seems to compile and run on my machine: please test. http://www.simutrans-forum.de/nightly/(So far this is only the GDI windows version, build with the ancient Debian stable mingw64 (gcc4.x or so)

Jenkins is not for running tests, it is for executing automated jobs based on various triggers (its original purpose and most common use probably is to run tests, though). I use it at work to do all the stuff required for building a release, as well as uploading that release to various servers. Basically everything that happens to the code post-commit. (Except getting the go-ahead to put new version into production from those I work for, who do some manual testing first, but even that is supposedly possible.)

A cross-compile environment on the other hand, does nothing by itself.

An easily automated test for Simutrans would be to check that committed code compiles for every supported architecture. Then the committer can get an e-mail if they broke something within minutes of doing it.

while setting up Jenkins with a build system looks like a many day job learning Jargon. Just a random line copyind from a short guide "Now that Jenkins is configured, you are ready to orchestrate or maintain a CI pipeline. I recommend checking out the Jenkins documentation Getting Started with Pipeline to create and deploy your first CI pipeline."

Sorry, if I get money for such nonsense, I can do this. But my time is limited and I do not work in development, so this is useless Jargon to me. The shell script is all I can do, and takes less than 10 minute to write.

Well, that shell script would be needed for Jenkins as well, except for the first three lines. In addition, it would not do the build if there are no changes, so that the dating of the files reflect when things last changed. And send e-mails to the guilty person(s) if the build fails due to compilation errors or whatnot. If all the developers were given access to its web interface, they would also be able to examine the logs and run builds manually to examine why the builds failed for platforms other than their own, or (less importantly) just to trigger release builds at different times.

So while Jenkins is a rather big tool with several features we don't need (and even more in plugins), I just thought such features out of the box would seem useful.

(Jenkins' new pipeline script system is indeed a lot to get familiar with, but I think they still support the old semi-point-and-click way of doing things.)

Anyway, no comments, but a complete (including packset installer) nightly is now generated at 2am MET (I think the server uses that for its crontab, not sure). Download at http://www.simutrans-forum.de/nightly/