It's interesting to read this #Semaphore #OSS announcement (https://semaphore.io/blog/semaphore-is-going-open-source) in the context of commoditising the complement (https://gwern.net/complement).
The only conclusion I can reach is that GH Actions has successfully monopolised the #CI market, so Semaphore give up and give away the software - commoditise CI - and pivot to enterprise support, where the real money is.
#CI
Take your Odoo development to the next level by automating code quality checks with pre-commit hooks and GitHub CI. Enforce standards, catch errors early, and streamline your workflow. #Odoo #DevOps #precommit #CI #Python
https://teguhteja.id/automate-odoo-code-quality-with-pre-commit/
With the addition of jruby 10.0.0.0 to our testing matrix, sentry-ruby now runs...
...128 test jobs 🙃
Luckily, with cached bundles, it takes less than 5 minutes to run ⚡
Na początek tego niecodziennego tygodnia link do prostej, ale konkretnej instrukcji, jak wykorzystać narzędzia CI/CD Gitlaba w celu wdrożenia swojej aplikacji (tutaj: napisanej w Javie).
https://bykowski.pl/ci-cd-dla-java-developerow-w-gitlabie-kompletny-scenariusz-w-6-krokach/
CI/CD для чайников — разберитесь, и начните автоматизировать рутину в разработке. Часть 3. Его величество, деплой
Пишу про полезные материалы про IT, и собираю свой ламповый нетворкинг тут - https://t.me/+434aQiGpZtAyNTU6 . Присоединяйтесь! Оглавление.
https://habr.com/ru/articles/904898/
#gitlabci #runner #cd #ci #react #nodejs #apache #ssh #деплой
(context: coding-trained LLM interaction, after I asked how short I can make a timeout for a tokio async test scenario):
LLM: 10ms is usually reliable unless running under heavy CI load.
Me: I'm an OG XP Programmer, "heavy CI load" is a misnomer! :-) continuous integration is a practice, not a tool.
LLM: True. CI is a discipline, not a server farm. Real XP: integrate always, test constantly, trust small, fast, deterministic tests.
Respect.
... Finally! someone respects my programming beliefs! 😂 😂 #programming #xp #ci #llm #tokio #rust
斉藤慎二被告がバームクーヘンを販売へ「取材はお受けできません」 (2025年4月25日掲載) – ライブドアニュース https://www.yayafa.com/2300682/ # #?u???o???? #Ci #entertainment #エンタメ
name a better feeling than finally seeing that green circle 🟢 #ci
I need to do CI with bleeding edge GCC and I finally decided to build the necessary container images for it:
🧱 cplusplus-ci/base – Ubuntu 24.04 + GCC 13/14, Clang 20/21
🔧 cplusplus-ci/latest – adds GCC 15 & trunk (built from source)
Perfect for matrix builds in GitHub Actions!
Example & details: https://github.com/mattkretz/cplusplus-ci
I have to say the "#workflows" offered by #github used for #CI builds are *very* useful.
After discovering some mishandling of build options in #swad, I decided to use their "matrix strategy" for testing some combinations of options automatically, and sure enough, this failed:
https://github.com/Zirias/swad/commit/b8cfb9c6db69d9593f39fc1503a388a4002471a3
Fixed in the next commit 😎
#NativeLink is an open source high-performance build cache and remote execution server, compatible with Bazel, Pants, Buck2, Reclient, and other RBE-compatible build systems. It offers drastically faster builds, reduced test flakiness, and support for specialized hardware.
@ar Lol, this is what I would have needed about 5 years ago to work around an issue with #GitLab and #CI.
Back then when you had a project with submodules (or just wanted to "git pull something" from within the CI it wouldn't be possible to do so over SSH. And for some reason it was not possible to pull via HTTPS to clients within that environment, so you basically had to manually edit the .gitsubmodules to relative paths after "git submodule add"-ing
(Don't know if it's fixed by now)
Klasycznie artykuły z rodzaju "najlepsze X w roku Y" klikają się bardzo dobrze, ale jeśli mają pomóc, to czemu nie. Tutaj mamy zestawienie popularnych narzędzi CI/CD, które w większości dobrze znacie, ale są też te mniej oczywiste.
https://www.codemotion.com/magazine/devops/top-10-ci-cd-tools-in-2025/
We’ve put the Go parallel test suite strategy to work at @Fleet —splitting Go tests into named groups and running them in parallel with GitHub Actions. 🚀 It’s made our CI faster, our feedback loops tighter, and our devs a lot happier! ⚡🧪
Give it a try and see the impact on your own CI pipeline! 💻✨
Article: https://victoronsoftware.com/posts/large-go-test-suite/
Video: https://www.youtube.com/watch?v=AFVlbf5LZwc
#Golang #CI #DeveloperExperience #SoftwareEngineering
Status update: I'm now automatically building and releasing a signed fork of stable moshidon with my patches. #CI is cool!
A reflection on difficult-to-build "open source" libraries.
I'm a bit skeptical about #CI. It seems like automatic build process lends itself to excessive configuration.
Therefore, cloning the repo and executing the standard build command for the toolchain does not simply work.
Then I have to troubleshoot. Which my hopeful ass DOES.
Or I could just delete it from my dependencies.
I think effective Software Freedom requires a painless build.
Are #FlakyTests disrupting your CI/CD pipeline & draining Developer Productivity?
Trisha Gee dives deep into the hidden impact of these non-deterministic tests.
Learn why ignoring them is a costly mistake for code quality, build times & your team's sanity.
▶️ Watch the full #InfoQ #podcast video: https://bit.ly/3Gf20lX
#timestamps included in the description
#CI #CD #DeveloperProductivity #DevOps #SoftwareTesting #CodeQuality
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.
GitHub suffers a cascading supply chain attack compromising CI/CD secrets
#HackerNews #GitHub #SupplyChainAttack #CI/CD #Security #Vulnerability #Cybersecurity
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst