vcs-git-shallow-clone : lp:~toabctl/launchpad-buildd : Git : Code : launchpad-buildd

Get this branch:: git clone -b vcs-git-shallow-clone https://git.launchpad.net/~toabctl/launchpad-buildd

Only Thomas Bechtold can upload to this branch. If you are Thomas Bechtold please log in for upload directions.

Branch merges

Merged into launchpad-buildd:master

Colin Watson (community): Approve on 2021-09-09

Branch information

Name:: vcs-git-shallow-clone

Repository:: lp:~toabctl/launchpad-buildd

Recent commits

7dacf15... by Thomas Bechtold on 2021-09-08

Add git_shallow_clone option to vcs_fetch() and use it for OCI build

Currently when cloning a git repository, the whole history is
cloned. That makes the cloning process slow (in case the repo is
large) and in some cases, the cloning fails due to its size (that's an
infrastructure problem but currently happens for OCI base images).
Just cloning the latest commit (via the "--depth 1" parameter)
improves the situation where large repos need to be cloned.

https://bugs.launchpad.net/launchpad-buildd/+bug/1939392

f1d287b... by Colin Watson on 2021-09-01

Release version 201

Merged from https://code.launchpad.net/~cjwatson/launchpad-buildd/+git/launchpad-buildd/+merge/407984

e025093... by Colin Watson on 2021-09-01

releasing package launchpad-buildd version 201

77fdfc1... by Colin Watson on 2021-09-01

Switch to "charmcraft pack --destructive-mode"

Merged from https://code.launchpad.net/~cjwatson/launchpad-buildd/+git/launchpad-buildd/+merge/407965

d8478e9... by Colin Watson on 2021-09-01

Switch to "charmcraft pack --destructive-mode"

This is safe now that Charmcraft 1.2 is in the stable channel.

a38370b... by Colin Watson on 2021-08-23

Sanitize non-user-bound macaroons in build logs

Merged from https://code.launchpad.net/~cjwatson/launchpad-buildd/+git/launchpad-buildd/+merge/407481

b4045e2... by Colin Watson on 2021-08-20

Sanitize non-user-bound macaroons in build logs

Some of the macaroons issued by Launchpad are not bound to a user, for
example if they're scoped to a particular running build. In those cases
the username part of the URL is empty. Fix build log sanitization to
remove these macaroons.

This is typically not a significant security issue since the macaroons
in question cannot be used after the build has completed, and anyone who
can see a build while it's in progress should normally also be able to
see the resources it uses, but nevertheless it wasn't intended behaviour
and is an unnecessary exposure of information.

76d9231... by Colin Watson on 2021-08-16