Allow delete old builds and workflows
M
Mateusz Loskot
Request
There have been number of requests to allow cleaning old builds, to list a few:
Option to prune branches from job listing (Oct 2015)
How can I remove an old branch (Dec 2015)
Allow manual pruning of stale branches (Jan 2016)
Hide automatically builds for deleted branches (Nov 2016)
Those threads have been closed automatically due to lack of updates (or discussion cleaning following the CircleCI 2.0 release). However, this feature has not been implemented or is not available, so I'd like to re-store the request here.
Motivation
First, this is a desired feature especially for teams using topic branches heavily (eg. w/ GitFlow, etc.).
Second, despite mentioned challenges to implement such feature, there seem to be agreement from CircleCI team members about validity of the request.
Finally, the backlog of comments to the linked threads suggests there is a demand for it from CircleCI users.
CCI-I-481
Merged in a post:
Possibility to remove old branches
M
Myroslava
As currently there is no such possibility, I believe this option can be useful for any developer.
CCI-I-1384
E
Etienne Marais
I would love this functionality to make it into circle please. We experiment with different workflows and would love the ability to delete old/stale and experimental branches along with their builds, artefacts, output logs etc. It eases the security conscious mind that old debug builds can be removed that if a breach occurs, the data is safe.
S
Sylvain Legault
There seems to be a bug where if you merge the PR while some task are running the circleci build will remain there even if there are no longer any related PR. As an administrator I should be allow to clean my dashboard without having to recreate the user branch. I'm not sure what are the challenge, if github can send a webhook when the build is removed, it should be just as simple as exposing the webhook to the dashboard.
P
Philip Kwesiga
Adding to this, there may be cases where certain information is printed especially for public repositories that should be concealed. Being able to delete or limit access to those particular workflows or builds would make less a thing to worry about.