Jump to content

Stan`

0 A.D. Project Leader
  • Posts

    17.043
  • Joined

  • Last visited

  • Days Won

    525

Posts posted by Stan`

  1. 9 hours ago, Vantha said:

    Sorry for the delayed reply.

    Yes, it also "works" in multiplayer. I think that's because winning players are not made observers at the end of the game. Actually, they should probably indeed be able to do it. Maybe the real bug here is that the button is deactivated.

     

    By it works do you mean other player see them, other observer see them or only you see them.

    See https://trac.wildfiregames.com/changeset/25761

  2. 1 hour ago, real_tabasco_sauce said:

    the scaling is just the recording (i think).

    These were things i did on mac but now cant on windows. (use numbers to shift queue batches).

    i havent tried cmd and ctrl, should that be done before or with the other keys?

    Oh you're on Windows ? Never mind my last comments then.

    • Like 1
  3. The installer is a standard NSI installer so the /S flag should work. https://github.com/StanleySweet/0AD-Chocolatey-Package/blob/master/0ad/tools/chocolateyInstall.ps1

    Another solution is to install it on one machine, zip the contents of the installation folder and deploy that everywhere, the game doesn't need any registry keys, and can even work as a portable version.

    Out of curiosity, would mind telling us the reason you need such a massive install ? 

  4. 2 hours ago, Norse_Harold said:

    I'd like to use my Gitea account to help identify issues with the new system, so please send the password.

    What's being used for CI/CD, still Jenkins, or something else? Where in the web-based interface is the CI/CD system? I particularly want to see whether warnings from source/tools/entity/checkrefs.py are being passed to developers effectively, as it's relevant to the changes to build/jenkins/pipelines/docker-differential.Jenkinsfile in D5266.

    Currently the CI/CD is not implemented, but yeah we'll probably use Jenkins. (There is new stuff like https://www.drone.io/ but everything is we currently have is for jenkins)

    For security reasons, I don't think we should run the CI with the Jenkinsfile on the branches (malicious actors might do bad things) If you want to test a new CI script you need access to the Jenkins instance or talk to someone who does.

    Regarding linting, it would be indeed interesting to have some better linting that what's currently done, where you have to check the linting on Jenkins. I've redirected error output to the correct stream, so you can technically get errors by filtering output 2. Currently IIRC the linting failing is not breaking the pipeline.

    Regarding that change, I'm a bit sad it went from -tax to -actx (cause tax is fun and so is tau (unused), but the rest looks okay)

  5. 6 minutes ago, Gurken Khan said:

    I can only guess what happened here, but if people just used the report function (check the three dots at the top right of every post!) they wouldn't need to quote anything.

    They did both :)

×
×
  • Create New...