On 24.08.20 18:15, Gylstorff Quirin wrote: > > > On 8/24/20 1:30 PM, Jan Kiszka wrote: >> On 24.08.20 13:25, Q. Gylstorff wrote: >>> From: Quirin Gylstorff <[email protected]> >>> >>> >>> Add the configration to run the ci builds on gitlab.com or on-premise >>> setups with >>> gitlab artifacts enabled. Each completed pipeline creates around 1.5 >>> GB aritfacts. >> >> Are those artifacts pushed around, to/from the gitlab instance? Our >> on-premise won't support that, others may not like it either. > The build uses the artifacts command to push them to the gitlab instance. > It is possible to use .gitlab-ci-no-artifacts.yml to avoid pushing > around the artifacts. This is the behaviour for our on-premise builds. > > If most people don't want to use the artifacts I can switch the default > to the old behavior.
Given the size, I'm inclined to make gitlab-native artifacts an opt-in and rather look for providing a pattern that allows storing them in S3, e.g., in case you have a cloud runner. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
