From 456f1f82946fdd9d72641bdf6a15f99cc1f8d186 Mon Sep 17 00:00:00 2001 From: Brian Hoffmann Date: Tue, 1 Jun 2021 11:40:08 +0200 Subject: [PATCH] Promote update scan to trial --- radar/2021-01-01/dependency-update-scan.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 radar/2021-01-01/dependency-update-scan.md diff --git a/radar/2021-01-01/dependency-update-scan.md b/radar/2021-01-01/dependency-update-scan.md new file mode 100644 index 0000000..24a4229 --- /dev/null +++ b/radar/2021-01-01/dependency-update-scan.md @@ -0,0 +1,10 @@ +--- +title: "Dependency Update Scan" +ring: trial +quadrant: methods-and-patterns + +--- + +Tools for automated dependency updates continue to offer a big productivity gain when integrated well into the build workflow. + +Nonetheless, this comes not without a word of warning. While it's great in theory, constant updates might quickly lead to a bombardment of merge requests. It is crucial that the chosen tools work reliably and are really well integrated. Otherwise, this might become overwhelming for teams. As an alternative, we also had good experience with disabled automatic merge requests and just manually triggered a job when we wanted to take care of the updates. \ No newline at end of file