lorenzogrv

We noticed the problem no longer persist after bumping our CI jobs to use `docker:20.10.23` with `docker:20.10.23-dind` service. Both cache exported and imported seem correct, build times reduced to a...

I'm commenting here because #8790 is closed by @mischnic, instructing to follow here. After resolving a failing build on ARM64 Graviton2 caused by huge memory usage (see comment at #5072),...

I dived a bit today. I could setup a dev environment for amd64 following your tips with success, but still need to figure out how to set up some of...

@mischnic Please reopen. Did not have time to dive more

Dropping a comment to get notified on updates

I'm researching about GitLab CI/CD components. I'm curious about why the include syntax is challenging. My understanding about: ```yaml include: - component: $CI_SERVER_HOST/$CI_PROJECT_PATH/$EXAMPLE@$REF ``` where: - `$CI_SERVER_HOST` points to GitLab...

I'm experimenting with the example at , it may fit.

@benedikt-bartscher Works like a charm, thanks for sharing. I used `gitlab-tags` as suggested by @mbrodala and release notes are actually included within MRs.

I can also confirm @fturmel 's workaround works for us with v `3.6.0`

I hit this today, and rebuilding the container (which also removes the .parcel-cache) worked out