Jump to content

Wikimedia Release Engineering Team/SpiderPig/Progress reports/2024-10-18

From mediawiki.org

Report on activities in the SpiderPig project for the week ending 2024-10-18.

[WE6.2.3] Create a new deployment UI

[edit]

If we create a new deployment UI that provides more information to the deployer and reduce the amount of privilege needed to do deployment, it will make deployment easier and open deployments to more users

  • Status: on track
  • Progress update
    • Lifecycle stage: Development
    • Design progress:
      • Added a couple Codex components to the Vue.js frontend; e.g., the buttons look Codex-like
      • Release Engineering and Design Systems (Ahmon and Eric) are pairing Monday to work on T375826—adding additional Codex components.
    • Added deployment status to the main page—it now says things like: "sync test servers", "sync proxy servers", "php restarts" during active deployment. The goal is that deployers should never need to watch the log, rather they are able to monitor a deployment at a high-level from a single page.
    • What's working, from a user perspective:
      • We have a Web UI using Vue and some Codex components
      • Users login with a time based one time password
      • The Web UI has a list of past deployments and their status, clicking a deployment opens detailed logs.
      • Users can specify a change to deploy.
      • Once submitted, the prompt for changes goes away and is replaced by a UI which prompts for confirmation then adds a deployment to the list as "in progress" and dynamically updates the "status"
      • Once a change is live on test servers, it asks the user to verify the change using WikimediaDebug and presents a dialog asking if the change looks right with Codex "Yes" "No" buttons.
      • If the user clicks "Yes" the deploy proceeds.
      • When the deploy finishes, the status of the deployment is "Complete," and the "Backport a change" form reappears.
    • What's still needed:
      • Codex styling.
      • Ensuring deployment of the tool is quick, even with added components.
      • And that's it for version 0.1.0.
  • Any new metrics related to the hypothesis
    • No
  • Any emerging blockers or risks
    • No
  • Any unresolved dependencies - do you depend on another team that hasn’t already given you what you need? Are you on the hook to give another team something you aren’t able to give right now?
    • No
  • Have there been any new lessons from the hypothesis?
    • No
  • Have there been any changes to the hypothesis scope or timeline?
    • No
Retrieved from "https://www.mediawiki.org/w/index.php?title=Wikimedia_Release_Engineering_Team/SpiderPig/Progress_reports/2024-10-18&oldid=6802232"