W dniu 31.08.2011 01:30, Alexander Sack pisze:

On Tue, Aug 30, 2011 at 6:55 PM, Zygmunt Krynicki<
zygmunt.krynicki@linaro.org> wrote:

Hi there.

The validation team has a new edge website, http://edge.validation.linaro.
**org/<http://edge.validation.linaro.org/> that reflects the development

trunk of all of our components. This site can be used to check latest
development effort, test bug fixes and, to some degree, use new features.

This website mimics the concept of now-defunct edge.launchpad.net. That
is, it allows for new code to run on top of the production database.

This has important ramifications:

1) Unsafe code could cause data loss
2) New features that depend on database schema modifications cannot be
tested this way.
3) Non-website features such as dispatcher and part of the scheduler cannot
be tested this way.

For addressing those we will soon deploy staging.validation.linaro.orgthat works on a periodic snapshot of the production database.

I will be posting an update with instructions on how to replicate this
setup if necessary and details about the periodic automatic roll out/upgrade
procedure.

Thanks for the heads up.

I wonder, once we have staging.v.l.o, do we really need edge anymore?

Perhaps not. We will see once we have both.

What problems does edge protect us from that we really care about? Maybe we
can avoid running 3 instead of two instances and have 3 instead of 2 code
rollout stages?

What do you mean by "rollout stages"?

my understanding is that with staging and edge you have three rollout steps/stages:

1. daily trunk
2. edge testing
3. production

i wondered about what risks the "edge" stage protects us from and if we can avoid that step as it comes with additional overhead on maintenance, process and time-to-production.