Applied patches from your ISV partner, but have you checked out the following steps?
We always have ISVs involved in most of our implementations. They too have their own cycles for ALMs, they too send across patches, updates, bug fixes and extensions. Then how do we tackle them? The above figure has a Dev branch where all your developers work, a Main branch which in turn is the gateway to higher environments, and an ISV branch to handle your ISV team's ALMs. a. The easiest way here is that we keep ISVs on a separate branch (let us call it ISV branch). We ask our ISV teams to deploy their changes out there. How to deploy their changes, is completely up to them, but mostly the easiest way to do this is to apply the package from LCS. The changes will automatically start showing as pending changes in the ISV branch. What are these changes be like: just compiled bin files. You log on to the dev VM that is mapped to this ISV branch. b. Check it into your ISV branch by tagging it into a pre-created DevOps task/Workitem and then noting the changeset thus created. Additio