I'd presume you'd be better to archive the build system yourself so you're not having to fight persistent changes, and changes that dramatically alter the build or interfaces as they adapted to evolving requirement by those actually directing the team, and paying for the work.
Honestly I wouldn't trust any of the parties involved to hold to something that increases their test/regression work load, or gets in the way of current priorities, or changes in direction.
If anything expect life-cycles to shorten, not expand.
