[00:50:59] !log tools.jouncebot Update to 01c73e0 [00:51:02] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools.jouncebot/SAL [02:20:13] !log tools restarting tools-db-1, oomkiller killed mariadb [02:20:16] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [05:08:00] bd808: That's noted! [11:27:10] Hey, any idea how to ask for image containers updates on Kubernetes? Last node18 image is soon one year old. [11:56:02] https://wikitech.wikimedia.org/wiki/Help:Toolforge/Build_Service#Tutorials_for_popular_languages [11:56:06] oh no [12:09:07] others tools to learn, what is this build service aaaaaaaaaaa [12:10:53] feel free to ask for help if you need it :) [12:11:56] just want to know if this is the new recommended way to follow, before burning everything at wmf data centers [12:12:00] by accident [12:12:38] i'm a hazard [12:12:58] it is yes, it's still being improved, but the features there are stable already [12:13:08] okayokay [12:13:47] Not sure I have time to learn all the stuff before tonight, might have to wait next week [12:15:07] "Builds aren't automatically triggered upon commit", does it mean there is something likely supported by the build service? [12:16:21] that's one of the missing features we are working on yes :) [12:16:38] (another one is automatic deployment after the build finishes) [12:18:44] okay okay, and how is handled the automatic-o-magic stuff about versions detection? [12:18:57] For example, for a nodejs app, should I use: https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version [12:19:13] or there is a toolforge-way recommended? [12:20:15] we are using that same buildpack, so yes, that should work (have not tested it myself yet) [12:24:10] For a more general question, is buildpacks the new tool the entire industry is shifting for devops? [12:24:35] Cause I am still stuck on image generation in a pipeline and pushed in a registry before deploying it [12:25:58] it is for platform-as-a-service stuff (heroku/cloudfoundry/pivotal/google engine/...) [12:26:44] the standards are pushed by the cloud native foundation https://buildpacks.io/ [12:29:33] okayokay, and what is the behind... behind the wmf platform? [12:30:00] I see that the Build Service is a Rust project, so it is something homemade? [12:30:15] https://gitlab.wikimedia.org/repos/cloud/toolforge/builds-builder [12:31:01] okay, just built on the top of k8s I guess [12:32:09] we are using a slightly modified version of the tekton pipeline that they give (https://github.com/tektoncd/catalog/tree/main/task/buildpacks), to build the images on k8s [12:34:15] we put an API (the bulids-api) in front of the k8s layer, and a client (toolforge build) so users don't need to pass/know all the options, do some setup toolforge-wise, and such [12:34:56] That's the funny thing, being a volunteer contributor developing tools on a WMF-managed environment is like being an intern and being overwhelmed because it's too professional an environment :d I guess I will learn a lot at least! [12:38:49] we are trying to make it as easy as we can :) if you have other ideas/input/suggestions please share, input is always appreciated [12:40:26] Not complaining, start of the learning curve of unknown tools is always harsh! [12:40:41] Can you say that it will stay for a bit? Like for the next years? [12:40:54] It could be a solide base [12:41:08] There are a lof of frwiki bots that should be migrated on Toolforge [12:41:21] This build service is a bit the answer for their complexe envs [12:41:32] and needs [12:42:53] we are planning on keeping it for a very long time yes, it should become the "default" toolforge way of building tools [12:43:33] noice [12:44:06] it's been >3years on the works xd [12:44:45] I've been pretty inactive for the two last years, so I missed a lot [12:44:49] good luck I guess :d [12:45:11] xd [12:46:23] T194332 the task is from 2018, that makes almost 6 years (it says 12 months project 🤦) [12:46:23] T194332: [Epic] Make Toolforge a proper platform as a service with push-to-deploy and build packs - https://phabricator.wikimedia.org/T194332 [12:46:50] It is labelled as Epic for a reason! [12:47:57] wait you are alone on it? [12:51:58] anyway, thanks for the answers/time, I will take some days to read about it, surely I am will be back until next week because I would have generated a blackhole at WMF hubs :D [12:52:04] have a nice end of week! [12:52:11] we are a few, but I'm the one putting most of the time there [12:52:14] you too! [12:52:41] it is on the right path! [17:42:12] !log tools reboot tools-sgewebgen-10-3 [17:42:15] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [22:59:23] Hello, world! Today: [22:59:25] FastCGI-stderr:PHP Fatal error: Uncaught PDOException: SQLSTATE[HY000]: General error: 1290 The MariaDB server is running with the --read-only option [22:59:38] (toolsdb) [23:02:11] !log tools rebooting tools-db-1 yet again [23:02:15] Iluvatar: I'm restarting, it'll be back shortly [23:02:16] Logged the message at https://wikitech.wikimedia.org/wiki/Nova_Resource:Tools/SAL [23:03:18] Iluvatar: should work now [23:03:36] Yes, thank you!