May 26 2020
May 11 2020
May 5 2020
Apr 1 2020
Mar 31 2020
Mar 23 2020
Mar 18 2020
If I'm understanding the task description correctly—inquiring about doing ephemeral chart-based deployments in CI for the sake of system/e2e testing?—then T244313: Experiment with different PipelineLib-/helm-based approaches to system testing might be relevant.
Mar 13 2020
Hand-wavy estimates using the GCS calculator have been sent to @thcipriani and @greg. Note that we haven't chosen a vendor at this point; The GCS calculator was simply the most convenient option available.
Mar 11 2020
See the task description for a draft (and very WIP) rewrite of the Seakeeper proposal.
Mar 6 2020
Reopening for follow-up patch review that schedules trigger builds on the master node.
This effectively limits the number of concurrent pipelinelib based jobs to 3 since contint1001 is configured with just 3 executors. Another approach we might take is to create a dummy node for trigger jobs that uses a second ssh connection to contint1001 (different user maybe) and has more executors assigned. The only concern there is that contint1001 would be allocating memory for a jenkins agent that does nothing.
Mar 2 2020
Feb 28 2020
The reference documentation on Wikitech should now be sufficiently dense, including all possible configuration fields and output variables. Since I did a substantial amount of refactoring and expanding, it would be for @LarsWirzenius to re-review.
Feb 26 2020
Feb 25 2020
Sounds good, @chasemp. Looking forward to giving this another go when we're ready.
Feb 21 2020
Thanks for the review, @LarsWirzenius!
@LarsWirzenius, thanks for reviewing!
Feb 19 2020
Stealing this from @mmodell since I broke the job (or hit a Zuul bug, rather) with the recent Zuul layout changes.
Feb 18 2020
Looks like the job filter introduced to zuul/layout.yaml in https://gerrit.wikimedia.org/r/c/integration/config/+/571849 that was meant to limit scheduling of the job for only changes to the includes/DefaultSettings.php file on wmf/* branches is not working.
I've written one very basic user guide which could use some review.
There are now three tutorials that could use some review before I close this out.
Today's re-roll of 1.35.0-wmf.19 showed no such increase in pool counter rejections nor spikes in restbase/varnish 500s.
Feb 13 2020
Relevant logstash range for restbase errors during the deployed period.
Feb 12 2020
Feb 7 2020
Feb 6 2020
Feb 5 2020
Thanks, @Jrbranaa. I'll set something up.
Jan 24 2020
Firstly, I just want to say thanks to @chasemp, @sbassett, @Reedy for taking the time to review the deep trove of meeting notes, supporting documents, and proposals around this year-long process of planning for the future of CI at WMF. As is often the case when making changes to such a widely utilized part of our developer ecosystem, there are some false starts, missing details, scope creep, revisions (revisions, revisions), and adaptions along the way. Making sense of such a large project at this point in the process is no small feat. So thank you for doing that work and for providing such a thorough and actionable response.
Jan 22 2020
Jan 21 2020
Jan 17 2020
Finished a second tutorial for introducing more concepts around multi-stage pipelines.
Jan 13 2020
Dec 20 2019
Finished a first draft at https://wikitech.wikimedia.org/wiki/Deployment_pipeline/Pipelinelib/Tutorial/TestingHelloNode
Dec 18 2019
Dec 16 2019
For CI systems that run on k8s, this might be useful: