Allow to remove CI build logs

It would be nice to have a feature to remove build log from the CI: this is useful in situation where by mistake some sensitive information was printed during build.

want to add: remove not only build logs but build it self. now you can "retry" build from the build page even if you rebased/deleted branch with commit with sensetive information.

Added ~19173 label

mentioned in issue #4313 (closed)

mentioned in issue #5572 (closed)

Reassigned to @grzesiek

@grzesiek We should also remove build artifacts.

@ayufan Sure, CarrierWave should take care about those files (artifacts and metadata) when destroying Ci::Build.

cc @creamzy

mentioned in merge request !2560 (merged)

Milestone changed to 8.5

mentioned in issue #4263 (closed)

Status changed to closed by merge request !2560 (merged)

mentioned in commit 62067b74

mentioned in commit 96158aa6

mentioned in issue #18138 (closed)

Is it also possible to delete external builds / pipelines?

@djanosik Sorry, not.

Mentioned in issue #25208 (moved)

Why not add remove builds pipelines feature?

In which version is this being added ? The only thing i can see here is deleting the build log, not the build itself ?

@pasnox It is not possible to remove pipelines or builds at the moment!

I mean you can erase build's content (build log, artifacts) but not remove it completely.

Got it , thanks

Gitlab allows deletion of build artifacts, but not the pipelines themselves. The build logs alone can take up many Gb of space. It it reasonable to delete these after a certain period? Ideally we'd like to only keep historic builds if they have a tag associated with them.

@gaff We plan to introduce the default artifacts expiration date in 9.0, so this might help!

@grzesiek The artifacts can already be configured to expire (or manually deleted). It's the pipelines and the logs associated with them that live forever. Any plans to fix this?

@gaff Currently it is only possible to erase build log + artifacts. It is not possible to remove builds or pipelines. I don't think we have an immediate plan to change that.

We plan to introduce the default artifacts expiration date in 9.0, so this might help!

@grzesiek Sweet! Do you have a link to an issue?

@JonathonReinhart https://gitlab.com/gitlab-org/gitlab-ce/issues/27762

@grzesiek - Just to put it in perspective our artefacts are a constant 4Gb (thanks to the expiry feature), but our build logs are 20Gb and growing!!

Any chance we could at least raise a feature request / keep this issue open to track it. Maybe other users have the same problem?

The 'data/gitlab-ci/builds' directory is at least sorted by date. Any harm in just zapping old stuff? Still I'd rather keep build logs for tagged builds if possible

@gaff I think it makes sense to have expiration setting for build logs, but this issue was used to track having a button to remove the log. Could you please create a new issue describing your need there? Thanks!

@godfat ok done - #28290 (moved) , let me know if you'd like to see anything else.

mentioned in issue #34295 (closed)

mentioned in issue gitlab#7278

mentioned in issue gitlab#8352