Clean up old builds

[bacongobbler]

Issue by technosophos
2017-04-20 22:40:22

---

Right now, each build creates at least one pod and one config map. Currently, for logging, these must persist "until the user is done with them" (e.g. until the logs are no longer relevant.

Really, we probably want to destroy the pod/configmap soon after it's run. But we can't really do this until we persist logging elsewhere

[bacongobbler]

Comment by jchauncey
2017-04-21 21:52:28

---

I would make this an option. That way people can inspect that state of a failed build and see what went wrong.

[bacongobbler]

Comment by bacongobbler
2017-07-04 23:22:55

---

We could add a configurable option like BUILD_HISTORY_LIMIT that limits the number of pod/configmap sets that are available to view from the most recent builds. That along with a plugin system to push logs offshore would ideally be the best of both worlds.

[bacongobbler]

Comment by technosophos
2017-08-30 15:39:34

---

At this point, we are setting a timestamp on secrets to indicate when it is safe to clean them up, but we still aren't automating anything.

[u2takey]

Comment by u2takey
2017-11-02 15:39:54

---

Should we add cmd delete/remove on brigage-client? For now, adding a cmd : clearall, which clean all brigage-related resource, will be very helpful for developers.

[technosophos]

The idea to make this a feature of brig is a great idea.

[technosophos]

brigade-vacuum now does the time-based cleanup. Marking this as closed.