Yep - my last comment here turns out to be wrong and I think this will work, getting a version of https://gerrit.wikimedia.org/r/c/mediawiki/core/+/508392 into shape.

See also: T216049: add CI job into operations/deployments-charts repo that helm lint packages and perform the helm index after merge.

As written originally:

Since we now have dev-images and Dockerfile contents don't live in the local-charts README, this should no longer be a problem.

See also: T216049

518333 checks that the configuration contains a top-level pipelines. A next step is turning the stage steps into individual classes with run() and validate() methods.

Planning to pair on this with @thcipriani this coming Friday.

I'm biased in favor of some non-JS solution partly because I'm not personally great at JS, but mostly because it feels like there's a lot of installation overhead there for something that needs to run easily on a client machine as part of a bootstrapping process. That said, I concur that we should give due consideration to languages already very well understood in our developer community.

Per conversation elsewhere, will pair with @thcipriani on the puppet role on Friday.

Just so I'm clear, in this instance is it sufficient to change workspace to /mnt/home/jenkins-deploy in the Jenkins config? I see that path exists.

How to change/update configuration

Cool. I'll push a patch for that shortly.

Taking a step back, I now wonder if we even need to install docker on host machines by default? Assuming people don't have to jump through any hoops to build images locally, which ideally should be the case...

Yeah, this seems worth exploring.

From docs:

We'll iterate on this, but it's working, at least.

Yeah, that seems correct.

The current state of local-charts meets these criteria for MediaWiki, though with more apparatus (Helm charts and installation scripts) than an individual Dockerfile.

See also: T218360

We (RelEng) are working on building Docker images for use with local-charts. Some goals:

@srodlund Thanks! We've let this drift a bit since I filed this task, but hopefully will get some momentum on it soon.

Could run into issue going down that route, as in order to run linux containers you'd need another VM?

I probably have a box somewhere around here I can install Windows on, FWIW.

"Spinnaker is an open source, multi-cloud continuous delivery platform for releasing software changes with high velocity and confidence."

Yep!

If anyone else would like to experiment with my demo installation, ping here or on IRC and I'll add your pubkey and write up quick SSH instructions.

I started with the official Quick-Start Installation and Tutorial, which is built around docker-compose.

Had some discussion here with friends who've worked in the iOS ecosystem. Consensus was pretty much that virtualization is difficult and they just use MacOS on Apple hardware. I don't think I learned anything unexpected here.

Yeah, it doesn't really seem like this fits under CI tooling. Seems to be a Gerrit-to-GitHub integration of sorts, run by GerritForge, who do hosted Gerrit. Updated spreadsheet accordingly.

sourcehut is a suite of interoperable tools for code hosting, issue tracking, CI, etc., described as "the hacker's forge". The web interface is minimal but effective. Individual components can be used standalone. The software overall is licensed AGPL, and a hosted / paid instance is available at sr.ht. Payment is optional on the hosted instance as the project is still in relatively early stages. From glancing over some of the repositories, it seems to be implemented largely in Python and Go.

Working build manifest: https://git.sr.ht/~brennen/blubber/tree/sourcehut_test/.build.yml