Integrate ofborg<->gerrit #5
Labels
No labels
Compat/Breaking
Difficulty
Architectural
Difficulty
Easy
Difficulty
Hard
Help Wanted
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Security
Status
Abandoned
Status
Blocked
Status
Need More Info
Status
Postponed
Tracking Issue
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: the-distro/infra#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
@JulienMalka said he was on it, can you update us on this?
(Related: the-distro/meta#2)
Nothing of significance yet, but I have taken my week from july 15 to 21 off to work full time on this, so expect updates at this point
Gonna tentatively assign this to you then. :)
Given the lack of update in the past month, desassigning, to give a chance to others to take this item, feel free to reassign if you are planning to do it imminently.
Still planning to complete this before end of month. If someone wish do to this before then, no problem.
As there's no progress shared, neither documentation / plan, it feels like to me this task was not started, feel free to re-assign yourself "just in time" when you are planning to start the work and share more about your plans/efforts, otherwise, someone else can take the lock in the meantime.
Well, whatever you might feel, I have actually started working on the task. I have been interrupted by vacations and was planning to finish when I am back home. As I said before, if someone wants to « take the lock » it’s perfectly fine.
If that's the case, please share progress, notes or code in visible ways, I am sorry to say you are not communicative enough. That's not fair to the rest of the members in this initiative.
This is not only about taking the lock or not, but letting others benefitting from your progress if there's any.
Please, consider to communicate the updated expectations in case they do not go as you intended initially, this is all what I'm asking.
Some progress sharing here as I took the lock some months ago.
OfBorg is partially (*) deployed in the infrastructure on bagel-box, a bunch of the code has been rewritten for VCS generalization.
Services handled by GitHub in the past have been stubbed with our own implementations: Pastebins et soon Status & Checks APIs.
GitHub support has been removed for now, but can be reintroduced at the cost of a better GitHub library.
@k900 contributed an asyncification of the codebase to Tokio.
(*) : deployed but unusable for now.
Next steps are:
(1) Stabilize the Gerrit event streamer and actually start inject events inside the various queues.
(2) Create a VCS event listener and dispatch jobs based on the generalized variant of a VCS event (that the Gerrit event streamer can send).
(3) Stabilize the Status & Checks API and write a Gerrit frontend plugin to load OfBorg status & checks on any CL.
Once we are there, we have a v1 of OfBorg that can be used experimentally, the first stage for experimentation will be Lix which is in dire need of a better CI as Buildbot has shown its limits.
Future roadmap once we validate all of this: