3 ms·
In general I agree -- but it means your pipelines will have to support every customer you deliver to and be version-aware. Part 11 of the FDA regulations that
by agentultra 7y ago
In general I agree -- but it means your pipelines will have to support every customer you deliver to and be version-aware.
Part 11 of the FDA regulations that oversee software compliance enforce expensive re-validation processes for every major release of software. It's not something your customers are going to want to do very often. So set up a CD for each customer on version X.y.z where X is static and make sure that you don't accidentally ship a backwards-incompatible major-version change on that pipeline.
It's an interesting challenge for operations-focused teams but I agree that CD is a valuable tool to have.
- deleted 7y ago[deleted]
- zbjornson 7y agoThis is a major problem and one of the artifacts of the reg not having been updated since 1997. The industry expectation for the validation process is for it to take four to six months, and it's specific to one version. We have 99.99% of our software requirements specification testing covered by several thousand automated tests that run in several minutes. Nonetheless, auditors have been wary of frequent updates, even though by their own admission our test strategy is far superior to any manual testing strategy and, critically, is the only realistic way to monitor for regressions specific to our usage of software that the vendor might not catch.
- agentultra 7y agoI don't disagree. The validation process is hilariously outdated as are the compliance requirements for software vendors. But it's ambiguous enough in places that we can adapt some modern operations tooling and practices to it.