At the moment deploying Bugzilla with FreeBSD's customizations requires several manual steps which is error-prone and requires manual rollback if things doesn't work out. bugmeister@ team needs to come up with automated way of single-command deployment and single-command rollback to previous working version. Using this command git version can be deployed to test instance and if it passes smoke test it can be deployed on main instance. This will make deploying new features and fixes a low-risk task unlike with the current state of affairs. I had some positive experience with Ansible[1] tool for automated deployments. And did some very basic prototyping[2] for Bugzilla setup. It's primitive at the moment but provides a general overview what playbook might look like. I'd like to get a feedback from team members before continuing this work. [1] https://www.ansible.com [2] http://people.freebsd.org/~gonzo/bugzilla.yml
^Triage: note the current status of this task is at https://wiki.freebsd.org/Bugzilla/Setup . - All the non-stock changes found on Production were upstreamed by me last year as part of FreeBSD Foundation-supported work. - The page includes all the steps to do it, as tested on a jail created solely to test if we can reinstantiate Bugzilla from upstream git repos. - The page includes some customizations that still need to be done manually. So, while the automation step is not completed, the manual steps have been cleaned up and documented.