Skip to content

Bug 42997: Only fetch the repository once on CI

Merge Info

Related Issues

Backporting

Timeline

  • Immediate: patchset needed as soon as possible
  • Next Minor Stable Release: patchset that needs to be verified in nightly before backport
  • Eventually: patchset that needs to be verified in alpha before backport
  • No Backport (preferred): patchset for the next major stable

(Optional) Justification

We want to backport this, because this causes significant slowdowns on Gitlab when we merge new rebases.

Merging

  • Merge to tor-browser - !fixups to tor-browser-specific commits, new features, security backports
  • Merge to base-browser - !fixups to base-browser-specific commits, new features to be shared with mullvad-browser, and security backports

Change Description

There is already a lot of context for this change over on the issue. See: #42997 (comment 3057581)

The tl;dr; is: we want to reduce fetching in CI as much as possible. To do that, I have implemented a new job that runs before all other jobs which does a fetch, then the repository is bundled and the bundle is shared with other jobs as an artifact making it unnecessary to fetch from Gitlab anymore. To further reduce fetching, in the setup job I generate a list of changed files and share that as an artifact with other jobs as well.

cc @lavamind for review.

How Tested

If CI passes we are golden.

Related to #42997 (closed)

Edited by Pier Angelo Vendrame

Merge request reports

Loading