Clobbering the Tree - Revision history

Djmitche at 18:24, 10 July 2012

2012-07-10T18:24:14Z

← Older revision		Revision as of 18:24, 10 July 2012
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://secure.pub.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.

Edmorley: Switch to https://secure.pub.build.mozilla.org/clobberer/

2012-07-09T15:39:04Z

Switch to https://secure.pub.build.mozilla.org/clobberer/

← Older revision		Revision as of 15:39, 9 July 2012
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/ . 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.

Mnoorenberghe: => https

2012-05-23T05:38:18Z

=> https

← Older revision		Revision as of 05:38, 23 May 2012
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 ~~http~~://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://build.mozilla.org/clobberer. 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.

Standard8 at 13:01, 16 April 2009

2009-04-16T13:01:31Z

← Older revision		Revision as of 13:01, 16 April 2009
Line 1:		Line 1:
			'''This page is only applicable to Firefox builds'''

	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.

Jesse at 07:07, 23 February 2009

2009-02-23T07:07:45Z

← Older revision		Revision as of 07:07, 23 February 2009
Line 10:		Line 10:

	Slaves are added to the database as they report in to ask for their clobber data, so it could take a little while for new slaves to appear all their branch / builder combinations.		Slaves are added to the database as they report in to ask for their clobber data, so it could take a little while for new slaves to appear all their branch / builder combinations.

			(See [[Build:ClobberingATinderbox]] for clobbering in CVS-based trees.)

Catlee: New page: 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. T...

2009-02-13T17:17:47Z

New page: 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. T...

New page

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 http://build.mozilla.org/clobberer. 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.

Selecting a builder-level checkbox merely selects all the slaves for that builder, and similarly, selecting the branch-level checkbox selects all the slaves for all the builders in that branch.

In addition, if a slave has not been clobbered in a configurable time period, it will clobber on the next run.

Slaves are added to the database as they report in to ask for their clobber data, so it could take a little while for new slaves to appear all their branch / builder combinations.