Shared Code Repo Different from Build Repo

ErinMB edited this page Mar 30, 2018 · 1 revision

Title: Repo for Shared Code Different from Repo the Product Org Uses in its Build

Statement of Problem: Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.

Context:
Shared code is kept in an accessible repository that is different from SCMs used by the products that use the shared code. Integration, testing and builds might be automated with the product SCM but not the shared code repo.

Forces: When the shared code is in a separate repository, any use of it could result in forking modifications, leading to complications later when the source is changed by the owning organization. When starting an inner sourcing program, it is possible there are many SCM systems in use; and, frequently, a new SCM is used for the inner sourcing program. Migrating from one SCM to another is not trivial. Since the using organization has a copy, they might not be aware of changes to the shared code. It is difficult and expensive for the using organization to change their automated build process to use a foreign repo.

Resolution:
Continuous integration, not only to with testing but also in production (aligns with DevOps). Known marker that shows the code hasn't been modified. Improved communication between teams. Accountability when you screw up; hold people accountable. Publish good stats about the negative implications of errors and processes for making this everyone's problem.

Resulting Context: Ideally, overhead is minimized or eliminated. Or integrate the shared code repository in the production build.

Author:

Status: Brain Stormed idea

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.