Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Cannot Remove Build History #8883

Open
akumaburn opened this issue Dec 12, 2017 · 27 comments
Open

[Feature Request] Cannot Remove Build History #8883

akumaburn opened this issue Dec 12, 2017 · 27 comments

Comments

@akumaburn
Copy link

Currently it is possible to delete build logs, but not the builds themselves.

As far as I can tell there is no way to delete build history and start fresh other than deleting a Repo completely from GitHub and creating a new Repo with the same name but this results in losing commit history on source control, renaming does not work.

@MikeGitb
Copy link

MikeGitb commented Feb 9, 2018

I'd also like to delete my old builds. Aside from the fact that they clutter the UI, I don't see, why travis needs to keep a complete history of my github commits, even if the branches and/or commits have long since been deleted.

@simonwep
Copy link

simonwep commented Apr 2, 2018

I also wish there where such an function, there are a'lot of old trash which looks really ugly. Anyway, they also keep stuff from Deleted branches... very messy.

@pzelnip
Copy link

pzelnip commented May 12, 2018

This would be extremely useful for those times when you have a contributor on a OSS project who opens a PR with a branch name that contains profanity & you want to remove that from the build history.

@stale
Copy link

stale bot commented Aug 10, 2018

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@stale stale bot added the stale label Aug 10, 2018
@pzelnip
Copy link

pzelnip commented Aug 10, 2018

Please don't close this.

@stale stale bot removed the stale label Aug 10, 2018
@MikeGitb
Copy link

Could we please have some official answer to this request instead of just closing it without a comment?

This stale bot seems pretty useless to me.

@simonwep
Copy link

Would be fantastic. Anyway, basically this isn't such a difficult feature request so it's odd that they haven't implemented it yet. Also there are alot of people who would appreciate such a feature.

@Tony-Ndichu
Copy link

Hey, why can't users delete their Travis CI build? I think its rather backward that you guys havent implemented this feature, I cant believe I have to delete an entire repo just to get a fresh build. Tsk tsk tsk

@tmonseigne
Copy link

I wan't to delete old builds (My first time with travis I have 40 failed build because I try some stuff with yml

@matthewdeanmartin
Copy link

In 2013, someone closed the exact same feature request because it wasn't on the road map. Here are the extreme that people are going to to delete an entry in build history- destroying their travis repo association & the corresponding github repo before recreating from scratch.

https://stackoverflow.com/a/52008929/33264

For me I had to turn of the auto building of pull requests. If I do a check in & garbage is created in the build history, that is my fault. But when a pull request happens and garbage is created in the build history, that is travis collaborating with pull request randos to do a denial of service on my travis account.

If we could hide builds for PRs and branches that don't exist anymore, that would help if actual deletion is somehow impossible.

@moikot
Copy link

moikot commented Mar 14, 2019

I totally don't understand why this is not on the roadmap. You would expect that you should be able to delete the builds you created explicitly or implicitly via commits.
The workaround with deleting and recreating your GitHub repo looks to me as if I would need to reimage my computer and restore all from a backup every time when I need to delete a file.

@Tony-Ndichu
Copy link

Tony-Ndichu commented Mar 15, 2019

I can't believe this still hasn't been implemented yet, its 2019 2020 guys

@simonwep
Copy link

simonwep commented Jul 2, 2019

Any updates @joshk or considerations regarding adding it to the roadmap?

@berendt
Copy link

berendt commented Nov 6, 2019

Too bad that this feature is still missing. We would like to be able to remove all information from repositories that we no longer use on Travis.

@cyberium
Copy link

Not yet implemented in 2020 :/

@willzhang
Copy link

Not yet implemented in 2020.2.12

@vaporyhumo
Copy link

I would love to see this too.

@Paulmburu
Copy link

am really longing for this

@edwrodrig
Copy link

Why this is not implemented?

@weidi97
Copy link

weidi97 commented Nov 2, 2020

I really need this feature!

@cenkbircanoglu
Copy link

+1

@simonwep
Copy link

Ya'll should check out GitHub actions, they're way better than using a third-party service and you can actually clear logs / remove workflows there. I started migrating all my projects to Actions and it works really well.

@berendt
Copy link

berendt commented Dec 10, 2020

@simonwep Confirmed. We are in the final stages of migrating everything from Travis CI to GitHub Actions.

@ddnexus
Copy link

ddnexus commented Apr 14, 2021

The date of this issue is Dec 12, 2017, and in all that time... not even a hint of an official answer.

It's interesting that there are many guys busy with their own jobs that find the time to answer in a couple of days max to every issues in their OOS projects (me included).

Even more interesting is that we don't run a business out of our projects. That makes me think...

Thank you @simonwep for the suggestion! The migration starts now ;)

@akumaburn
Copy link
Author

The date of this issue is Dec 12, 2017, and in all that time... not even a hint of an official answer.

It's interesting that there are many guys busy with their own jobs that find the time to answer in a couple of days max to every issues in their OOS projects (me included).

Even more interesting is that we don't run a business out of our projects. That makes me think...

Thank you @simonwep for the suggestion! The migration starts now ;)

There seems to be an inverse relationship between making money and caring about users if the industry is anything to go by..

@borys-pc33
Copy link

borys-pc33 commented Feb 9, 2022

How would it happen that this is still not solved in 2022?

@ddnexus
Copy link

ddnexus commented Jan 15, 2024

2024! 🤣🤣🤣

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests