We have a beta version of the tool here https://beta-videocuttool.wmcloud.org/, although setting it up can be a task in itself
Lets try to automate the updation of the code in beta version, and later sync up prod with beta as well
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Added fixes for beta servers | labs/tools/VideoCutTool | master | +103 -20 | |
Add beta version to VCT | labs/tools/VideoCutTool | master | +15 -13 |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Gopavasanth | T327582 Improve the functionality of VideoCutTool | |||
Resolved | Reputation22 | T333466 [GSOC 2023 Proposal] Improve the functionality of VideoCutTool | |||
Resolved | Reputation22 | T342373 Setup beta version for VideoCutTool and sync it |
Event Timeline
Here's the workflow I've been thinking
After stabilizing the VCT in beta, lets run a crontab task for every 2/3 hours, which basically runs git pull gerrit master (updates the codebase at beta)
and later sync this in prod as well
If anyone has other thoughts/ideas on how to sync beta (beta-syncing), lets discuss it here :)
Change 940484 had a related patch set uploaded (by Reputation22; author: Reputation22):
[labs/tools/VideoCutTool@master] Add beta version to VCT
Change 940484 abandoned by Reputation22:
[labs/tools/VideoCutTool@master] Add beta version to VCT
Reason:
Change 940494 had a related patch set uploaded (by Sohom Datta; author: Sohom Datta):
[labs/tools/VideoCutTool@master] Added fixes for beta servers
Change 940494 merged by jenkins-bot:
[labs/tools/VideoCutTool@master] Added fixes for beta servers