In a few hours we'll touch the basics of creating a Dagger module.
This will be an live hands-on to be followed with a remastered video for impatient users!
https://www.youtube.com/live/uTV-49mS_7k?si=ixXbk9RJCeaIAt8O
In a few hours we'll touch the basics of creating a Dagger module.
This will be an live hands-on to be followed with a remastered video for impatient users!
https://www.youtube.com/live/uTV-49mS_7k?si=ixXbk9RJCeaIAt8O
AWS CodeBuild now supports parallel test execution!
Speed up CI pipelines by running tests in parallel—less waiting, faster feedback.
#CI #github il est désormais possible d'utiliser des versions "free-threaded" de #Python (sans le global interpreter lock, qui bride la façon de faire de l'exécution concurrente) dans les #githubactions
https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/
GitHub 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.
https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/
The mobile #CI space is plateauing, and we might be on the verge of a DevX innovation in mobile tooling. Let me explain why.
Keep your commits consistent!
forgejo-commit-path-rules
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: https://codeberg.org/kemitix/forgejo-commit-path-rules
A ForgeJo Action/CLI Tool
What's New:
- Coloured highlights in logging (supports --no-colour
)
- all
matching strategy for paths (default is any
)
- Built in templates: docs
, feature
, tests
and fixes
Usage:
- Define rules in .forgejo/commit-path-rules.toml
- Run via CLI or ForgeJo Action
Install:cargo install forgejo-commit-path-rules
CLI Usage:forgejo-commit-path-rules --workspace . --no-colour
Forgejo Action:
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
Some valuable advice on #CI - see below for the source:
---
After years of dealing with this (first Jenkins, then GitLab, then GitHub), my takeaway is:
* Write as much CI logic as possible in your own code. Does not really matter what you use (shell scripts, make, just, doit, mage, whatever) as long as it is proper, maintainable code.
* Invest time that your pipelines can run locally on a developer machine as well (as much as possible at least), otherwise testing/debugging pipelines becomes a nightmare.
* Avoid YAML as much as possible, period.
* Don't bind yourself to some fancy new VC-financed thing that will solve CI once and for all but needs to get monetized eventually (see: earthly, dagger, etc.)
* Always use your own runners, on-premise if possible
ACCU 2025 SESSION ANNOUNCEMENT: Continuous Integration (CI) for large scale package-based C, C++ projects with Conan2 by Diego Rodriguez-Losada
Register now at https://accuconference.org/booking/
FLOSS Weekly Episode 825: Open Source CI With Semaphore - This week, Jonathan Bennett and Ben Meadors talk to Darko Fabijan about Semaphore,... - https://hackaday.com/2025/03/19/floss-weekly-episode-825-open-source-ci-with-semaphore/ #hackadaycolumns #flossweekly #semaphore #podcasts #ci/cd
You wanted Java 24? How adorable.
Fun fact: Ancient relics like Maven happily obey any Java version , but modern, cutting-edge tools. Gradle, AWS Lambda, and more require new releases just to function.
Because nothing says progress like mandatory dependencies.
Meanwhile, Kubernetes & Maven sit back, laughing.
They do whatever they want.
They are independent.
Unlike you.
#DevLife #ProgrammingMemes #SoftwareEngineering #CodeHumor #programming #coding #Maven #Gradle #AWSLambda #DevOps #DependencyHell #CI/CD #BuildFails #JustDevThings #Relatable #WhyIsThisSoAccurate #EngineerCult
Can't wait for all the #bugs, #security holes, and #vulnerabilities that will inevitably come out because people are just letting some prediction engine write their code for them and aren't reviewing the code or the logic being inserted into it. #AI #LLM #Vibe #SoftwareDevelopment #CI
https://developers.slashdot.org/story/25/03/18/1428226/vibe-coding-is-letting-10-engineers-do-the-work-of-a-team-of-50-to-100-says-yc-ceo
For years, teams using Xcode faced vendor lock-in with CI providers. However, as the market becomes commoditized and more options arise, consider reclaiming that freedom:
https://tuist.dev/blog/2025/03/11/own-your-automation
#ci #automation
Update to #WoodpeckerCI v3.4.0! Enjoy customizable repo output format, backoff retry for store setup, and more!
#release #CI #DevOps
the other #rustlang thingy that's been cooking (and just passed a #ci run) is called #taggart.
it uses #tengri to pop up an interactive table to edit things, namely: the #id3 tags of music releases
its 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 #faircamp instance! but none of it's well-tagged and existing interactive mediatag editors are ugh
howdy folk first passing #ci build of #tengri just now:
https://codeberg.org/unspeaker/tengri
this is the framework code ripped out of #tek, my #tui #daw. currently, it wrapps #ratatui and provides main loop, generic layout logic, and an #sexpr-based mini-#dsl for describing stuff
(some ci run, not even outputting coverage like it ought to, but i don't feel like debugging that right now - PRs welcome!)
@metacosm Chez #Github, ils poussent à l'usage des #actions, des bouts de #CI réutilisables fournis par eux ou par la communauté. C'est possible aussi avec #Gitlab, facilement, mais je trouve qu'ils y poussent moins.
Chez #Gitlab, tu as des _jobs_ dans des _stages_, clairs, faciles, lisibles.
Chez #Github tu as des _steps_ dans des _jobs_ eux mêmes rangés dans des _worflows_ appelant potentiellement des _actions_, bordélique, foutraque.
Gave my first ever #lightning #talk in #FOSSASIA Summit 2025. Pretty nervous and excited. But went well. Some snaps of that in Day 3.
@fuchsiii @grumpygamer oftentimes said cores ain't even "dedicaded" but shared...
"shared core VPS" are a very big mistake, espechally on Hosters like #Hetzner...
So OFC said systems are overworked, espechally the convenience-based options where one just shoves on files and tells it to "bake it"...
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 sent a notification once done.