Change Details

This is the first step to making it easy to add new automation. We can leverage our existing build infra to easily make small gains in our existing automation (update-manpages chosen as a proof-of-concept): * Automation timeouts are now configurable rather than hidden away in Teamcity * Improved readability of the automation logic compared to the current switch-case in a bash file. * If needed, build templates can be leveraged for automated commit builds as well. The next step is to integrate preparation of the git commit into the config, along with the necessary machinary to make that happen.

This is the first step to making it easy to add new automation. We can leverage our existing build infra to easily make small gains in our existing automation (update-seeds chosen as a proof-of-concept): * Automation timeouts are now configurable rather than hidden away in Teamcity * Improved readability of the automation logic compared to the current switch-case in a bash file. * If needed, build templates can be leveraged for automated commit builds as well. The next step is to integrate preparation of the git commit into the config, along with the necessary machinary to make that happen.

This is the first step to making it easy to add new automation. We can leverage our existing build infra to easily make small gains in our existing automation (update-manpagesseeds chosen as a proof-of-concept): * Automation timeouts are now configurable rather than hidden away in Teamcity * Improved readability of the automation logic compared to the current switch-case in a bash file. * If needed, build templates can be leveraged for automated commit builds as well. The next step is to integrate preparation of the git commit into the config, along with the necessary machinary to make that happen.