How are people getting round broken indexes when doing automated builds? We use mercurial and cruise control to deploy. The database is shared however one thing we have found is after build on the dev site search breaks becuase the index is no longer there or corrupted so you have to after a build rebuild the index.
I tried checking in the index from my local machine and sometimes that works others not (think issues are todo with locking and segments).
Don't check your index in, it should reside only on the environment it's meant to be on.
We manage a separate index on local vs dev vs staging vs live, this way the data in the index represents that environment.
If you're really concerned about the index being out of date after a deployment you could drop a web.config value that's read on application start that will force a rebuild of the index.
Examine in build environment
How are people getting round broken indexes when doing automated builds? We use mercurial and cruise control to deploy. The database is shared however one thing we have found is after build on the dev site search breaks becuase the index is no longer there or corrupted so you have to after a build rebuild the index.
I tried checking in the index from my local machine and sometimes that works others not (think issues are todo with locking and segments).
Regards
Ismail
Don't check your index in, it should reside only on the environment it's meant to be on.
We manage a separate index on local vs dev vs staging vs live, this way the data in the index represents that environment.
If you're really concerned about the index being out of date after a deployment you could drop a web.config value that's read on application start that will force a rebuild of the index.
Slace,
Awesome suggestion will put this into practice high 5 u rock!!!
Regards
Ismail
is working on a reply...