The docs we have are:
Start there and improve if needed.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Stalled | LucasWerkmeister | T320140 Migrate wd-shex-infer from Toolforge GridEngine to Toolforge Kubernetes | |||
| Resolved | matmarex | T319707 Migrate dtcheck from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320062 Migrate steve-adder from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | None | T320011 Migrate rfa-voting-history from Toolforge GridEngine to Toolforge Kubernetes | |||
| Open | dcaro | T194332 [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs | |||
| In Progress | dcaro | T267374 [tbs.beta] Create a toolforge build service beta release | |||
| Resolved | dcaro | T331323 [tbs] Everybody has deployed every component once in toolsbeta | |||
| Resolved | Slst2020 | T331327 [tbs] Slavina has deployed every component in toolsbeta | |||
| Resolved | Slst2020 | T331343 [tbs] Slavina has deployed the webservice cli in toolsbeta |
To generate the debian changelog on macOS, I used lima-vm: https://github.com/lima-vm/lima
$ limactl start --> choose Debian --> edit ~/.lima/debian/lima.yaml to make the directories you need writable ... $ limactl shell debian $ sudo apt update && sudo apt upgrade -y $ sudo apt install git-buildpackage $ export NAME="your-name" $ export EMAIL="your-email" From the webservices repo: $ EDITOR=true gbp dch -R --id-length=7
id_length and other config can also be put inside a gpt.conf file inside the debian folder comtaining the changelog, e.g.
[DEFAULT] ignore-branch = True id-length = 7