Zeitpunkt Nutzer Delta Tröts TNR Titel Version maxTL Di 23.07.2024 00:00:20 983 0 67.739 68,9 toot.BERLIN 4.2.10 500 Mo 22.07.2024 00:01:34 983 0 67.681 68,9 toot.BERLIN 4.2.10 500 So 21.07.2024 00:01:21 983 0 67.703 68,9 toot.BERLIN 4.2.10 500 Sa 20.07.2024 00:01:15 983 0 67.611 68,8 toot.BERLIN 4.2.10 500 Fr 19.07.2024 13:57:57 983 0 67.571 68,7 toot.BERLIN 4.2.10 500 Do 18.07.2024 00:00:03 983 0 67.456 68,6 toot.BERLIN 4.2.10 500 Mi 17.07.2024 00:00:50 983 0 67.400 68,6 toot.BERLIN 4.2.10 500 Di 16.07.2024 00:01:21 983 +1 67.400 68,6 toot.BERLIN 4.2.10 500 Mo 15.07.2024 00:01:12 982 0 67.399 68,6 toot.BERLIN 4.2.10 500 So 14.07.2024 00:00:02 982 0 67.309 68,5 toot.BERLIN 4.2.10 500
Benjamin (@blindcoder) · 04/2017 · Tröts: 961 · Folger: 252
Di 23.07.2024 10:19
Dear GitLab CI experts: I want to run a pipeline based on the state of the previous run.
Say, if a file config/foobar.json changed since the last run, I want to do something with it, how would I go about it? Would I use a "cache" as defined by GitLab?
There are potentially hundreds of these files, with new ones getting added or old ones deleted, each triggering a specific action.
[Öffentlich] Antw.: 1 Wtrl.: 2 Fav.: 0 · via Web