Continuous integration and a build server are of more value the more remote contributors there are. Or I suppose if you have very large and slow to build content. Or, if you are using a Homebrew code base in which you have to invent the whole content Pipeline and build process. However if you're a solo developer using say unity, and have an empty new project, I do not feel like there is any value (correct me if I'm wrong) to set up a build server and continuous integration. As you yourself are building whenever you make a change, and that happens automatically when you run it.
Imo, making it while it's still simple is the best moment to start :-)
The main benefit in CI/CD lies with not forgetting about running tests, and checking whether it compiles outside of your working computer. Also, if you're making for something different than a computer - web/mobile/console - the more easy it is to actually test your game the better.
Projects with many different target platforms, and projects with many collaborators, both greatly benefit from having tests that are run continuously on commits, and continuous builds, for sure.
A multiple platforms slipped my mind. I've worked on games targeting PC and all consoles, and breaking one while fixing the other was a common occurrence because actually opening the solution for all of them and building all of them on every line change would have been bad for workflow.
ABC - Always Be Compiling
Continuous integration and a build server are of more value the more remote contributors there are. Or I suppose if you have very large and slow to build content. Or, if you are using a Homebrew code base in which you have to invent the whole content Pipeline and build process. However if you're a solo developer using say unity, and have an empty new project, I do not feel like there is any value (correct me if I'm wrong) to set up a build server and continuous integration. As you yourself are building whenever you make a change, and that happens automatically when you run it.
Imo, making it while it's still simple is the best moment to start :-)
The main benefit in CI/CD lies with not forgetting about running tests, and checking whether it compiles outside of your working computer. Also, if you're making for something different than a computer - web/mobile/console - the more easy it is to actually test your game the better.
Projects with many different target platforms, and projects with many collaborators, both greatly benefit from having tests that are run continuously on commits, and continuous builds, for sure.
A multiple platforms slipped my mind. I've worked on games targeting PC and all consoles, and breaking one while fixing the other was a common occurrence because actually opening the solution for all of them and building all of them on every line change would have been bad for workflow.