Page MenuHomePhabricator

Wikimedia Technical Conference 2019 Session: WMF CI 2.0: Status and future
Closed, DeclinedPublic

Tokens
"Meh!" token, awarded by zeljkofilipin."Cookie" token, awarded by brennen."Love" token, awarded by hashar."Yellow Medal" token, awarded by kostajh."Love" token, awarded by Florian.
Assigned To
Authored By
debt, Oct 4 2019

Description

Session

  • Track: Deploying and Hosting
  • Topic: WMF CI 2.0: Status and future

Description

CI Futures Working Group/RelEng reports on what has been done since the WG report has been published, what decisions/conclusions were reached, what's coming up next and in what timeline
https://www.mediawiki.org/wiki/Wikimedia_Release_Engineering_Team/CI_Futures_WG/Report

It's likely worth mentioning explicitly that we've landed on Argo, after building out and evaluating proofs-of-concept for our final three candidates (Argo, Zuul v3, GitLab CI).

Questions to answer and discuss

Question:
Significance:

Question:
Significance:

Related Issues

  • ...
  • ...

Pre-reading for all Participants


Notes document(s)

[link to notes document (gdoc and / or etherpad)]

Notes and Facilitation guidance

https://www.mediawiki.org/wiki/Wikimedia_Technical_Conference/2019/NotesandFacilitation


Session Leader(s)

  • [name]
  • [name]

Session Scribes

  • [name]
  • [name]

Session Facilitator

  • [name]

Session Style / Format

  • [what type of format will this session be?]

Session Leaders please:

  • Add more details to this task description.
  • Coordinate any pre-event discussions (here on Phab, IRC, email, hangout, etc).
  • Outline the plan for discussing this topic at the event.
  • Optionally, include what this session will not try to solve.
  • Update this task with summaries of any pre-event discussions.
  • Include ways for people not attending to be involved in discussions before the event and afterwards.

Post-event summary:

  • ...

Post-event action items:

  • ...

Event Timeline

debt created this task.Oct 4 2019, 3:27 PM
Florian added a subscriber: Florian.
hashar awarded a token.Oct 7 2019, 8:16 PM

Folks who attended the New CI Working Group meetings are sparsely represented at Tech Conf; however, I'd love to talk about the work of that group at a high level.

@hashar has unique insight and depth of knowledge about our current CI that will undoubtedly be useful in this session. Also, he was involved in the discussions of the New CI group.

It's likely worth mentioning explicitly that we've landed on Argo, after building out and evaluating proofs-of-concept for our final three candidates (Argo, Zuul v3, GitLab CI).

Some more background reading:

hashar updated the task description. (Show Details)Oct 11 2019, 6:58 PM
hashar added a subscriber: dduvall.Oct 11 2019, 7:03 PM

@brennen I have copy pasted your comment to the task description.

Guess we can go listing the key requirements we had and then go with some summary of why Argo has been selected. Would be nice to list out the features it has and how it matches our use case. I think @dduvall had some graph showing the Argo architecture which can give some hint.

I guess we can start gathering questions and have answers presented during the session. Some kind of live Q&A would be nice probably.

Guess we can go listing the key requirements we had and then go with some summary of why Argo has been selected.

💯

greg closed this task as Declined.Oct 16 2019, 5:02 PM

This session is being subsumed into the broader T234641 session on Continuous Delivery/Pipeline.