Blogged about progress and status quote of Ambient, my CI engine.
https://blog.liw.fi/posts/2025/ambient/
#Ambient #AmbientCI #CI #ContinousIntegration #ContinuouslyIrritating
When debugging failures in CI in steps that execute a shell snippet, it's harder to do when stdout and stderr aren't interleaved. This leads me to think about this: what would the ideal CI run log output be like, for me? I have some thoughts that I'll write down when I have time, but you, dear reader, what is your answer? Assume anything is possible, don't worry about how much work it'd be.
@chris Paul refers to #ContinousIntegration which I'll write here as an hashtag so that clicking/tapping on it should ask your #Fediverse client to search for more messages containing it, and maybe help you understand more, if interested 🤗
My team is doing continuous integration for years. Trunk-based. PRs is a tool invented for OSS development in a zero trust environment.
When working in a team and doing pair or mob programming, practicing TDD, no need for code reviews and no need for PRs or branches.
Just once in a while, we create a branch for some exploratory work.
But this is an exception.
If a random person gives you source code and asks to debian package it, is there any proper way to install it's Build-Depends with apt beforehand?
I've only found some shady scripts that extract the field. What would be the proper debian way to do it?
In case anyone is looking for a selfhosted #CI for #nixos: I just build a adapter for #woodpecker
It consumes #nixos #flakes and dynamically generates a #pipeline from a predefined output. That way, you can define all your build steps as #nix code or derive them from the flake's contents.
https://github.com/pinpox/woodpecker-flake-pipeliner
#continous #integration #continousintegration @WoodpeckerCI #pipeline
Woodpecker configuration Service to dynamically generate pipelines from nix flakes - GitHub - pinpox/woodpecker-flake-pipeliner: Woodpecker configuration Service to dynamically generate pipelines f...
I wrote a Gitlab CI pipeline to build, test and deploy my app - here are
3 things I learnt about #gitlab CI
- reusing jobs with "extends"
- #junit integration
- speeding up the cache
https://on-sw-integration.epischel.de/2022/12/29/3-things-i-learnt-about-gitlab-ci/