Figure out shared workspace situation on deploy master
Closed, DeclinedPublic
Actions

Assigned To

Authored By

	• demon
	Nov 13 2015, 5:50 PM

Description

Right now we use /srv/mediawiki-staging/ as a combination deployment directory and workspace for deployers. This becomes problematic over time when we're trying to do things like co-masters (T104826: [scap] Add support for syncing /srv/mediawiki-staging including fully working git data to warm spare deploy server). It's already gotten messy in production a couple of times, and in beta with T117016: beta-scap-eqiad mira / deployment-bastion permissions problem. Places we have problems:

Setting mtimes (you have to be an owner to set them)
Bad umasks causing people to create/steal ownership? I know this has been mentioned previously.
People can edit the repo at the same time, leading to inconsistent and confusing states.

Mentioned Here: T104826: [scap] Add support for syncing /srv/mediawiki-staging including fully working git data to warm spare deploy server
T117016: beta-scap-eqiad mira / deployment-bastion permissions problem

• demon raised the priority of this task from to Needs Triage.

• demon updated the task description. (Show Details)

• demon moved this task to Needs triage on the Scap board.

• demon subscribed.

• demon set Security to None.

This was kind of a hand wavey bug filed as a result of the linked tasks in the opener. Won't really be happening.