Page MenuHomePhabricator

[EPIC] Create a development staging environment and branch.
Closed, DeclinedPublic

Description

As an engineer I want a development staging environment so that I can code review and merge my patches from development and have them publicly visible without being bound to the release cycle.

As a tech lead / product owner I want to be able to functionally test (QA) patches in an environment without them being bound to the release cycle, so that I can sign off on them and control when they go to the release production environment (beta cluster).


Outcomes:

  • A development environment is set up with our extensions and dependencies.
  • How it was set up, and where it is, is publicly documented on-wiki.
    • Any engineer knows how to set one of these up or clean it up in case of mess-up.
  • Development is redirected to the development branch (gerrit patches merge to development).
  • Development env auto-updates from the development branch continuously and stays in sync with the top of the HEAD of development.
  • Environment is filled with sample pages/articles.

Related: T100296 [EPIC] Create a formal release process for MobileFrontend/Gather

Event Timeline

Jhernandez claimed this task.
Jhernandez raised the priority of this task from to High.
Jhernandez updated the task description. (Show Details)

We (Release-Engineering-Team) had a project last quarter to create a staging cluster, basically a new and improved version of the beta 'deployment-prep' cluster. The project got put on hold because it turned out to be a huge undertaking and we didn't have the resources to get everything finished.

If some other teams want to help pick up this project and see it through to completion, we certainly have made a lot of progress already and that work shouldn't left to languish for long.

If some other teams want to help pick up this project and see it through to completion, we certainly have made a lot of progress already and that work shouldn't left to languish for long.

See https://phabricator.wikimedia.org/tag/staging/

We did a naive attempt at T104324 with the reading maintained extensions (
http://reading-web-staging.wmflabs.org/wiki/Main_Page) which is obviously
easy to set up. Obviously setting up a staging environment for all the
organization is a huge task :(

I would definitely love to see this tackled as an organizational level, and
having each department owning setting up their respective software and
helping in the process.

We don't have much specific knowledge on ops but if there's something
specific we can help with please ping us.

We're trying to kickstart several efforts to improve infrastructure, for
example T104561 for setting up a common way for teams to specify sets of
test data to import into instances.

ATM we're "hold on" in actually splitting the branches, we'll continue to
talk and consider it moving forward.

Thanks for your comments.