3

You need to separate the 2 concepts a bit: the integration part - how are the changes integrated into your master branch (or some other integration branch, that's also possible), which may be continuous or not. Technically neither approach you describe is actually continuous integration unless your feature branches have a very short lifespan - typically ...


3

From my experience this is very provider specific and requires evaluating the SLA offered for a particular service. For example the siteground cloud server offerings shown at https://www.siteground.com/cloud-hosting.htm state: We preinstall and maintain all the software you need on your server. While offerings from liquidweb they make it clear they will ...


2

... by making a minor change in the v1 front half, this breakage can be avoided. The above excerpt of this queston reminds me of something similar from around the late 90s, say 1996-1999 (when zillions of ITers were preparing for Y2K ...). In those days, new software releases of huge software vendors would come with release notes that included things like ...


1

Do not trigger Build 2 automatically from Build 1. Instead add a last step to Release 1 to queue Build 2. There are a few ways to do it, e.g. https://stackoverflow.com/questions/52821204/how-to-queue-build-pipeline-as-task-from-release-pipeline


Only top voted, non community-wiki answers of a minimum length are eligible