Closed Bug 956788 Opened 10 years ago Closed 6 years ago

Allow slaveapi to clobber its build directory and reboot

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: armenzg, Unassigned)

Details

On bug 956013, a win7 machine got disabled because the C:\slave\test\build directory could not be removed.

I wonder if it would help to have an API that would clobber a slave, enabled it and reboot it into production.
I agree, this would be a useful thing for SlaveAPI to be able to do. We have to be very careful here, though, because if we allow for deletion of arbitrary files it would be easy to exploit and eg, rm -rf /. One way to work around this would be only allow deletion of files under certain paths. Eg, only files under the slave's basedir or /tmp. We'd also want to blacklist deletion of buildbot.tac, I think.

This could probably go under an endpoint such as /slaves/$slave/actions/rm, and accept a list of files/directories in the POST arguments.
Component: Tools → General
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.