canmove, Confirmed users
1,394
edits
Clobbering the Tree: Difference between revisions
no edit summary
m (=> https) |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
Occasionally a build directory on a machine needs to be "clobbered". This means that the entire directory hierarchy, including the checked-out source and object directory, are deleted. | Occasionally a build directory on a machine needs to be "clobbered". This means that the entire directory hierarchy, including the checked-out source and object directory, are deleted. | ||
To clobber a build directory on a particular machine, or all the machines doing builds of a particular type (build, or unittest for example), or all the machines on a particular branch, you can visit https://build.mozilla.org/clobberer. You need a valid LDAP account to access this page. | To clobber a build directory on a particular machine, or all the machines doing builds of a particular type (build, or unittest for example), or all the machines on a particular branch, you can visit https://secure.pub.build.mozilla.org/clobberer/ or, easier to remember, http://clobberer.pub.build.mozilla.org. You need a valid LDAP account to access this page. | ||
If you check a box next to one of the slaves on a particular branch / builder, then the next time that slave runs a build on that branch, it will first delete the entire build directory, and then do a fresh checkout, and continue on with the rest of the build. | If you check a box next to one of the slaves on a particular branch / builder, then the next time that slave runs a build on that branch, it will first delete the entire build directory, and then do a fresh checkout, and continue on with the rest of the build. | ||