Shakedown Social

Hugo van KemenadeGitHub Actions now supports free-threaded Python!I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.<a href="https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/</a><a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://mastodon.social/tags/FreeThreaded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeThreaded</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a>

Paul Campbell🔥 Keep your commits consistent! 🔥 <code>forgejo-commit-path-rules</code> v0.2.3 ensures your commit messages align with your file changes.🧩 Enforce commit message and file path rules in your repo!🦀 Written in Rust ⭐ Repo: <a href="https://codeberg.org/kemitix/forgejo-commit-path-rules" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/kemitix/forgejo-commit-path-rules</a> 🎬 A ForgeJo Action/CLI Tool✨ What's New:- Coloured highlights in logging (supports <code>--no-colour</code>) - <code>all</code> matching strategy for paths (default is <code>any</code>) - Built in templates: <code>docs</code>, <code>feature</code>, <code>tests</code> and <code>fixes</code>🛠 Usage:- Define rules in <code>.forgejo/commit-path-rules.toml</code> - Run via CLI or ForgeJo ActionInstall: <code>cargo install forgejo-commit-path-rules</code>CLI Usage: <code>forgejo-commit-path-rules --workspace . --no-colour</code>Forgejo Action:<pre><code> jobs: validate: steps: - uses: actions/checkout@v3 with: fetch-depth: 0 - name: Run forgejo-commit-path-rules uses: kemitix/commit-path-rules@v0.2.3 with: args: --verbose </code></pre><a class="hashtag" href="https://mitra.kemitix.net/collections/tags/rustlang" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#ForgeJo</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/ci" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/cli" rel="nofollow noopener noreferrer" target="_blank">#CLI</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/git" rel="nofollow noopener noreferrer" target="_blank">#Git</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/codeberg" rel="nofollow noopener noreferrer" target="_blank">#Codeberg</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/opensource" rel="nofollow noopener noreferrer" target="_blank">#OpenSource</a>

IT NewsFLOSS Weekly Episode 825: Open Source CI With Semaphore - This week, Jonathan Bennett and Ben Meadors talk to Darko Fabijan about Semaphore,... - <a href="https://hackaday.com/2025/03/19/floss-weekly-episode-825-open-source-ci-with-semaphore/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackaday.com/2025/03/19/floss-weekly-episode-825-open-source-ci-with-semaphore/</a> <a href="https://schleuss.online/tags/hackadaycolumns" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hackadaycolumns</a> <a href="https://schleuss.online/tags/flossweekly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#flossweekly</a> <a href="https://schleuss.online/tags/semaphore" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#semaphore</a> <a href="https://schleuss.online/tags/podcasts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#podcasts</a> <a href="https://schleuss.online/tags/ci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ci</a>/cd

stateful beingthe other <a href="https://mastodon.social/tags/rustlang" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rustlang</a> thingy that's been cooking (and just passed a <a href="https://mastodon.social/tags/ci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ci</a> run) is called <a href="https://mastodon.social/tags/taggart" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#taggart</a>.it uses <a href="https://mastodon.social/tags/tengri" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tengri</a> to pop up an interactive table to edit things, namely: the <a href="https://mastodon.social/tags/id3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#id3</a> tags of music releasesits purpose? why, to make it easier to prepare a certain pile of content (that we've accumulated with a friend over the past, what, 6-7 years), for publication in a sovereign <a href="https://mastodon.social/tags/faircamp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#faircamp</a> instance! but none of it's well-tagged and existing interactive mediatag editors are ugh<a href="https://codeberg.org/unspeaker/taggart" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://codeberg.org/unspeaker/taggart</a>

Kevin Karhan :verified:<a href="https://oxytodon.com/@fuchsiii" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@fuchsiii</a> <a href="https://mastodon.gamedev.place/@grumpygamer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@grumpygamer</a> oftentimes said cores ain't even "dedicaded" but shared...<ul><li>In the case of <a href="https://infosec.space/tags/CyberBunker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberBunker</a> they literally sold <a href="https://infosec.space/tags/Nehalem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nehalem</a>(-EX) hardware to customers (cross referenced by datasheets/specsheets and the fact they never updated the listings in 15+ years!)</li></ul>"shared core VPS" are a very big mistake, espechally on Hosters like <a href="https://infosec.space/tags/Hetzner" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hetzner</a>...<ul><li>Ask me how I know!</li></ul>So OFC said systems are overworked, espechally the convenience-based options where one just shoves on files and tells it to "bake it"...<ul><li>OFC it shouldn't be the responsibility of a <a href="https://infosec.space/tags/GameDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GameDev</a> to <a href="https://infosec.space/tags/DIY" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DIY</a> one's <a href="https://mastodon.gamedev.place/@grumpygamer/114158849810039330" rel="nofollow noopener noreferrer" target="_blank">own</a> <a href="https://infosec.space/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> / <a href="https://infosec.space/tags/CD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CD</a> infrastructure, and I think given the size and complexity of said games it would be overkill to do so.</li></ul>If feasible, just grab' yourself a decently performing PC/Server/Laptop you can chug in a closet, SSH/RDP onto and use it as "build servant" ("Rechenknecht") to run your builds and then <a href="https://ntfy.sh" rel="nofollow noopener noreferrer" target="_blank">sent a notification</a> once done.<ul><li>Since speed is of no real concern, but <a href="https://infosec.space/tags/EnergyConsumption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EnergyConsumption</a> is (@€0,33/kWh), I got some <a href="https://infosec.space/tags/fanless" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fanless</a> <a href="https://infosec.space/tags/ThinClient" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThinClient</a> as a <a href="https://infosec.space/tags/MiniServer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MiniServer</a> with some external SSD plugged into USB 3.0</li></ul>

Xanatos :godot:I just tried to update my Godot project to Godot 4.4 but it seems like my build pipeline does not support 4.4 builds just yet ...Somehow the docker container was not updated because a service broke down, now I need to wait.<a href="https://github.com/felix-schindler/build-godot-action" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/felix-schindler/build-godot-action</a>I already used a fork of the action because the other one was achieved.Are there other more reliable build solutions out there?<a href="https://mastodon.gamedev.place/tags/Godot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Godot</a> <a href="https://mastodon.gamedev.place/tags/Godot4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Godot4</a> Godot4_4 <a href="https://mastodon.gamedev.place/tags/GameDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GameDev</a> <a href="https://mastodon.gamedev.place/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://mastodon.gamedev.place/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Development</a> <a href="https://mastodon.gamedev.place/tags/GodotQuestion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GodotQuestion</a>

Paul Campbell🧩 <code>forgejo-todo-checker</code> v1.3.2: Checks your source files for TODO and FIXME comments, where they don't have an open issue number🦀 Written in Rust ⭐ Repo: <a href="https://codeberg.org/kemitix/forgejo-todo-checker" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/kemitix/forgejo-todo-checker</a> 🎬 A ForgeJo Action.What's new- bug fix - hadn't updated the version of rust used in the docker imageInstall<pre><code>cargo install forgejo-todo-checker </code></pre>CLI Usage<pre><code>forgejo-todo-checker --workspace $PWD \ --site https://git.kemitix.net \ --repo kemitix/forgejo-todo-checker </code></pre>This should allow you to check locally that your <code>TODO</code> and <code>FIXME</code> comments are valid before you push the change to your CI.CI<code>forgejo-todo-checker</code> is primarily a Forgejo Action:<pre><code>jobs: tests: steps: - name: Checkout uses: actions/checkout@v4 - name: Check TODOs uses: kemitix/todo-checker@v1.3.2 </code></pre>If you have any <code>TODO</code> or <code>FIXME</code> comments in your code that doesn't have an associated and open issue, then this will fail the build.<a class="hashtag" href="https://mitra.kemitix.net/collections/tags/rustlang" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#ForgeJo</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/ci" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/cli" rel="nofollow noopener noreferrer" target="_blank">#CLI</a>

⁂Krafty⁂Update on <a href="https://fosstodon.org/tags/Nautilism" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nautilism</a>, my Godot sailing game! I have refactored the wave code and made some more under-the-hood tweaks. I also set up a <a href="https://fosstodon.org/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> <a href="https://fosstodon.org/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> pipeline to automatically build the game and host the builds on <a href="https://fosstodon.org/tags/gitlabpages" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitlabpages</a>. The repository is <a href="https://gitlab.com/TKK13909/nautilism" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/TKK13909/nautilism</a> and the website is <a href="https://nautilism-c15fcc.gitlab.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nautilism-c15fcc.gitlab.io/</a>Please try it out and tell me what you think! I'm still trying to figure out the direction I want to take the game but I am happy to hear suggestions.<a href="https://fosstodon.org/tags/GameDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GameDev</a> <a href="https://fosstodon.org/tags/Godot" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Godot</a> <a href="https://fosstodon.org/tags/Sailing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Sailing</a>

Raphaël 🇺🇦 🇪🇺How many projects or CI stacks, critical or not, in production or not, rely on some Dockerfile starting with "FROM alpine:xxx" ?<a href="https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://alpinelinux.org/posts/Seeking-Support-After-Equinix-Metal-Sunsets.html</a><a href="https://bzh.social/tags/alpinelinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#alpinelinux</a> <a href="https://bzh.social/tags/docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#docker</a> <a href="https://bzh.social/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://bzh.social/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dev</a> <a href="https://bzh.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webdev</a> <a href="https://bzh.social/tags/saas" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#saas</a> <a href="https://bzh.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://bzh.social/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a>

small circle 🕊 in calmnessThe typical <a href="https://social.coop/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FOSS</a> <a href="https://social.coop/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dev</a> lifecycle:1. <a href="https://social.coop/tags/showerthought" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#showerthought</a> idea 2. git init, start <a href="https://social.coop/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> pipeline 3. code, don't forget <a href="https://social.coop/tags/TDD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TDD</a>It is great for doing what you love to do as a coder: <a href="https://social.coop/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a>. It is less great if over time your coded work becomes popular, and all kinds of boring other considerations must be dealt with.One easily ends up in a <a href="https://social.coop/tags/OneManArmy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OneManArmy</a> situation, and if not delegating timely, on a burnout vector.This kind of ad-hoc <a href="https://social.coop/tags/ShowDontTell" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ShowDontTell</a> also leads to <a href="https://social.coop/tags/TechnosphereMyopia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TechnosphereMyopia</a>: tech-only perspective.

Mark GardnerYesterday I had the privilege of attending a very informative presentation on <a href="https://social.sdf.org/tags/GitLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitLab</a> pipelines and <a href="https://social.sdf.org/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> (continuous integration) for <a href="https://social.sdf.org/tags/Perl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Perl</a> <a href="https://social.sdf.org/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developers</a> by Gábor Szabó.<a href="https://youtube.com/watch?v=RnXwP4I-vUs" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://youtube.com/watch?v=RnXwP4I-vUs</a>If you’re at all interested in improving the reliability of your Perl code and *leveling up* from “software <a href="https://social.sdf.org/tags/developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#developer</a>” to “software engineer," you owe it to yourself to watch Gábor’s talk!<a href="https://social.sdf.org/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#programming</a> <a href="https://social.sdf.org/tags/coding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#coding</a> <a href="https://social.sdf.org/tags/SoftwareDevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareDevelopment</a> <a href="https://social.sdf.org/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SoftwareEngineering</a> <a href="https://social.sdf.org/tags/git" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#git</a>

gary<a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@geerlingguy</a> sometimes forks are just too good opnsense vs pfsense is a good example, rsj should start wearing a shirt that says lucky. pls do followup on making minirack for specific use cases and matched up with the odd hw/sw req - add in a couple usb - one for dx and another for iso/backups <a href="https://infosec.exchange/tags/minirack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#minirack</a> blends <a href="https://infosec.exchange/tags/ci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ci</a>/cd <a href="https://infosec.exchange/tags/open" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#open</a> source hw <a href="https://infosec.exchange/tags/object" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#object</a> orientated <a href="https://infosec.exchange/tags/partimage" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#partimage</a> <a href="https://infosec.exchange/tags/dd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dd</a> piped through gz

Kevin Bowen :xfce:Also, for <a href="https://fosstodon.org/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> tasks, you've got to add a line to install `poetry-plugin-export` since that is no longer included in Poetry core(e.g. if you are exporting into a requirements.txt to create a venv for testing).A shell has also been move out of core, you'll need `poetry-plugin-shell`.<a href="https://fosstodon.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a>

Paul Campbell🧩 <code>forgejo-todo-checker</code> v1.3.0: Checks your source files for TODO and FIXME comments, where they don't have an open issue number 🦀 Written in Rust ⭐ Repo: <a href="https://git.kemitix.net/kemitix/forgejo-todo-checker" rel="nofollow noopener noreferrer" target="_blank">https://git.kemitix.net/kemitix/forgejo-todo-checker</a> 🎬 A ForgeJo Action.What's new:- add cli args to help run locallyInstall:<pre><code>cargo install forgejo-todo-checker </code></pre>CLI Usage:<pre><code>forgejo-todo-checker --workspace $PWD \ --site https://git.kemitix.net \ --repo kemitix/forgejo-todo-checker </code></pre>This should allow you to check locally that your TODO and FIXME's comments are valid before you push the change to you CI.CI:<code>forgejo-todo-checker</code> remains primarily a Forgejo Action:<pre><code>jobs: tests: steps: - name: Checkout uses: actions/checkout@v4 - name: Check TODOs uses: kemitix/todo-checker@v1.3.0 </code></pre>If you have any TODO or FIXME comments in your code that doesn't have an associated and OPEN issue, then this will fail the build.<a class="hashtag" href="https://mitra.kemitix.net/collections/tags/rustlang" rel="nofollow noopener noreferrer" target="_blank">#RustLang</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/forgejo" rel="nofollow noopener noreferrer" target="_blank">#ForgeJo</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/ci" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a class="hashtag" href="https://mitra.kemitix.net/collections/tags/cli" rel="nofollow noopener noreferrer" target="_blank">#CLI</a>

Kevin Karhan :verified:To answer <a href="https://fedi.rrr.sh/@pearl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@pearl</a>'s original <a href="https://fedi.rrr.sh/@pearl/113709160592615810" rel="nofollow noopener noreferrer" target="_blank">question</a>:<ul><li><a href="https://infosec.space/tags/pfSense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pfSense</a> & <a href="https://infosec.space/tags/OPNsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OPNsense</a> allow importing and exporting the entire systems configuration as a single <a href="https://infosec.space/tags/XML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#XML</a> file and <a href="https://infosec.space/tags/tnsr" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tnsr</a> should have support for <a href="https://infosec.space/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a>... </li></ul>Maybe <a href="https://mastodon.social/@geerlingguy" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@geerlingguy</a> is having a closer look at <a href="https://infosec.space/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> / <a href="https://infosec.space/tags/CD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CD</a>-ing <a href="https://infosec.space/tags/SDN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SDN</a> distros.<ul><li>Personally, I'd stick to non-automated but well documented networking <a href="https://www.youtube.com/@LAWRENCESYSTEMS" rel="nofollow noopener noreferrer" target="_blank">like</a> <a href="https://infosec.space/tags/LawrenceSystems" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LawrenceSystems</a>.</li></ul>

Stefan EissingI love how fast the curl CI jobs have become. In less than 5 minutes, we see success or failures in more than 100 build combinations. Huge.Many thanks to <a href="https://mastodon.social/@vsz" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@vsz</a> for the heavy lifting! <a href="https://chaos.social/tags/curl" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#curl</a> <a href="https://chaos.social/tags/ci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ci</a>

Jan Wildeboer 😷:krulorange:Time for a hot cocoa and deep sleep after this old man has yelled at clouds to get <a href="https://social.wildeboer.net/tags/woodpecker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#woodpecker</a> <a href="https://social.wildeboer.net/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> to work without throwing a warning. Ultimately it was a mixture of typos and not optimal documentation for a IMHO breaking change in handling secrets. But it's sorted thanks to the patience of virtual friends who squirmed along with me. The whole little drama at <a href="https://social.wildeboer.net/@jwildeboer/113641515179786589" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://social.wildeboer.net/@jwildeboer/113641515179786589</a> :)

Hugo van Kemenade<a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bagder</a> During November 2024, the <a href="https://mastodon.social/tags/CPython" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPython</a> project ran exactly 96,697 CI jobs on GitHub.That's an average of 134 CI jobs/hour.The average run-time per job was 5m 37s.That means we spent 13.97 days of CPU time per day.<a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://mastodon.social/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a>

Ariel (🐿 arc)What are folk's approaches to integration testing against cloud stuff?For example we have an Enterprise Application as an IdP in AzureDo you usually mock it out? Have a long-lived nonprod instance? Terraform spin up and tear down?<a href="https://eigenmagic.net/tags/AWS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AWS</a> <a href="https://eigenmagic.net/tags/Cloud" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cloud</a> <a href="https://eigenmagic.net/tags/Testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Testing</a> <a href="https://eigenmagic.net/tags/DevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevOps</a> <a href="https://eigenmagic.net/tags/IntegrationTesting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IntegrationTesting</a> <a href="https://eigenmagic.net/tags/PlatformEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PlatformEngineering</a> <a href="https://eigenmagic.net/tags/CICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICD</a> <a href="https://eigenmagic.net/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://eigenmagic.net/tags/ContinuousIntegration" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ContinuousIntegration</a>

183231bcbAI email clients are officially outdated and being replaced by CI email clients. CI stands for "Cat Insertion." Are you trying to read an email? A picture of a cat is overlaid on top, blocking half the message. Are you trying to write an email? Our CI autocomplete helpfully inserts cat pictures that have nothing to do with what you were trying to write. You can opt out of CI features in settings if you're a Luddite who hates progress, but our app will forget your settings every time you relaunch it. Also, all release notes are now written by cats. Currently, our advanced CI features are only available on our email client. However, if you give us $1,000,000,000 in venture capital money, we hope to expand to put CI into a web browser, a word processor, a video chat meeting client, an operating system, and even hardware! The future is meow. <a href="https://transfem.social/tags/Caturday" rel="nofollow noopener noreferrer" target="_blank">#Caturday</a> <a href="https://transfem.social/tags/CI" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://transfem.social/tags/AI" rel="nofollow noopener noreferrer" target="_blank">#AI</a>

Recent searches

Search options

Administered by:

Server stats:

#ci