diff options
| author | vandebo@chromium.org <vandebo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-06 01:53:24 +0000 |
|---|---|---|
| committer | vandebo@chromium.org <vandebo@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-06 01:53:24 +0000 |
| commit | 1cc4cec99777d7731af17de4607874196c42d7d9 (patch) | |
| tree | 46394fddb7fab3635b58f1e9543bea6b8222832b /DEPS | |
| parent | 96efe1c207a43c16c49f52b72e4ff4811cd1338b (diff) | |
| download | chromium_src-1cc4cec99777d7731af17de4607874196c42d7d9.zip chromium_src-1cc4cec99777d7731af17de4607874196c42d7d9.tar.gz chromium_src-1cc4cec99777d7731af17de4607874196c42d7d9.tar.bz2 | |
Revert 166085 - Selective build clobbering feature (landmines.py and android build scripts).
It looks like this made win extract_build fail.
Adds the ability for devs/troopers/etc. to set 'landmines' in the tree so that
the build will selectively clobber when a builder moves over a revision with such
a change.
This cl has an basis landmines.py, and hooks the clobber mechanism to the android
build scripts.
The relevant cl which implements this for
compile.py is here: https://chromiumcodereview.appspot.com/11234013/
I'm planning to also implement an informational invocation for gclient to let devs know
about any potential landmines so they can decide if they need to clobber.
R=cmp,maruel@chromium.org
BUG=121897
Review URL: https://chromiumcodereview.appspot.com/11175016
TBR=iannucci@chromium.org
Review URL: https://codereview.chromium.org/11293111
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@166105 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
| -rw-r--r-- | DEPS | 5 |
1 files changed, 0 insertions, 5 deletions
@@ -631,9 +631,4 @@ hooks = [ "pattern": ".", "action": ["python", "src/build/gyp_chromium"], }, - { - # Check for landmines (reasons to clobber the build). - "pattern": ".", - "action": ["python", "src/build/landmines.py"], - }, ] |