Infrastructure around game development with unity

News & General Discussion
1

Hi guys, im interested in what infrastructre you use around unity. I mean things project plannig, task/ticket management, automated builds, testing or deployment. Do you use things like Gitlab? MS Team Foundation Server? What about tickets/milestone? What do you use for version control? How do you to handle the binary files? Where do you host yor repository if you have one? Whats the workflow with artists and designers? Stuff like that.

This mainly out of curiosity :).

2

Don’t have answers for all of these, but:

  • I use HacknPlan for project management. It’s designed for game development and works quite well.
  • Git for source control without any web hosting - just local. I back up the project and repository both locally and to offsite locations.
  • I just include the binary files in git - haven’t really noticed any major issues, but I don’t have huge numbers of large assets either.
3

Pixel Crushers projects use:

  • Git repos with Visual Studio Team Services
  • Trello for project management
  • Mantis for support cases
  • uTomate for automated testing, builds, and deployment

A couple large (20+ GB), non-Pixel Crushers projects that I’m collaborating on use:

  • Subversion (artists’ preference) on private servers
  • Trello for project management and knowledge bases (although I’d consider HacknPlan for future projects)
  • Slack for discussion and planning. It’s also useful to pass ownership of scene editing so only one designer at a time makes changes to a scene. We make heavy use of prefabs so this isn’t too big a problem.

Like Dave-Carlile, we haven’t had any problems with binary files. On a fairly regular basis (3 times/year), I test a full local wipe and re-download from the repo for peace of mind.

1 Like
4

I also use Git via Visual Studio Team Services. That also comes with some basic project/task management tools which I’ve been using for some projects quite effectively.

I’m also using Quip for chat, planning and documentation. It’s really good at some things, but lacklustre elsewhere and doesn’t seem to have budged in the time we’ve been using it, so we’re likely to go elsewhere, (Some of the built in tools are too basic to cover our needs, and we’re not splitting things over different tools, so at some point we’ll probably just move.)

In the past I’ve used Jira and Atlassian’s other tools for planning and issue tracking. Good stuff, highly recommended, though perhaps not warranted until you’ve got some fairly process-driven development going on. So great for large projects, perhaps not of much practical benefit to small ones.

1 Like