T
Tim Hutchens
Guest
In general, I agree that a *single* ABL program should never be deployed alone. However, what about that bug that makes it through all the builds/tests and is only discovered by an end user? You can't prevent all bugs. Suppose this bug is high-impact. We'll need to point fingers later, but right now we need to fix the bug and deploy immediately. How does one deploy a fix for that high-impact bug immediately to stop the leak? The fix should ultimately make its way through the regular build process that compiles everything and runs all the tests, but sometimes you know what's wrong, fix it, and need to deploy it now - not in 20 minutes or 2+ hours. What's more important - following the letter of the law on CI/CD process, or getting your application back online? I feel like this type of scenario is what Dmitri is encountering. Rereading your post, @dbeavon, it sounds like breaking up the code base is part of the answer, but that could certainly be a challenge to do as well (and maybe more work than figuring out the file dependencies). Tim
Continue reading...
Continue reading...