Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
sbws
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 132
    • Issues 132
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #33121

Closed
Open
Opened Jan 31, 2020 by juga @jugaMaintainer11 of 19 tasks completed11/19 tasks

Deploy sbws in the rest of bwauths

When we're ready to deploy sbws in all the remaining bwauths (3/6), send an email to the dirauths to start the transition process.

The plan right now is to deploy every new change in only one bwauth, wait 5 days or a week, then test the next.

We're going to use longclaw's sbws to deploy the new changes.

Currently, these are the new changes we should test:

  • !9 (merged)
  • !14 (merged)
  • !15 (closed)
  • !16 (merged)
  • !18 (merged)
  • #29710 (closed)
  • #33198 (closed)
  • #33947 (closed)
  • #40008 (closed)
  • #40038
  • #40041 (closed)
  • #40043
  • #40044
  • #40048 (closed)
  • #40049
  • #40051
  • #40059
  • #40060
  • #40061

If all goes good, we should then update maatuska.

If all goes good, other bwauths can change to sbws, one by one.

Note that this was a parent ticket for many others mentioned by @tracbot at #33121 (comment 2518949), very similar to the https://gitlab.torproject.org/tpo/network-health/sbws/-/issues?label_name%5B%5D=sbws-roadmap tickets and %sbws: 1.1.x-final milestone

Edited Feb 22, 2021 by Georg Koppen
Assignee
Assign to
sbws: 1.1.x-final
Milestone
sbws: 1.1.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/network-health/sbws#33121