AJR/TechRadarAJR
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add some more articles

Browse Source
This commit is contained in:
Daniel Pötzinger
2017-03-31 09:27:03 +02:00
parent 24628cc38f
commit ff6b9f3988
17 changed files with 147 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
radar/2017-03-01/pin-external-dependencies.md
View File

@@ -17,6 +17,6 @@ We suggest the following:
* Keep the dependency definition AND the lock file in version control. This ensures that chained dependencies are also locked and you have changes of that file visible in your version control commit history. This helps finding issues or bugs that might relate to unintended updates in external modules or transient dependencies.
* Build Step: The application build step should use the the pinned versions (with the help of the lock file) to ensure that the same revisions of the dependent packages are used.
* It's also suggested to use local or central caches for the retrieval of packages. (E.g. [artefactory as composer and npm cache](https://extranet.aoe.com/confluence/display/knowledge/Artefactory))
* It's also suggested to use local or central caches for the retrieval of packages. (E.g. [artifactory as composer and npm cache](/platforms-and-aoe-services/artifactory.html))
For updating of dependencies define a process in the team. This can either be done on the dev-system or in a seperate automated CI job - both resulting in updated dependency definitions in the applications VCS.