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.

#CI #continousIntegration

@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 🤗

#MastodonTips #FediverseTips

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.

#swdev #DEVCommunity
#PairProgramming #ContinousIntegration

https://martinfowler.com/articles/ship-show-ask.html

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?

#debian #packaging #continousintegration

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

quote from pentest report (asked if this is ok):

:ablobcatpopcorn:​ (great work, sadly NDA'ed)

"We bypassed the internal SSH Zero Trust Gateway because its service account was setup to fully trust the [...] Continuous Integration. Due to the chosen Zero Trust gateway this compromise was undetectable, because there are no logon events on the target Linux systems being recorded [... This had been disabled by the admins because there was no log investigation procedure for this.]"

#zerotrust seems to have basic requirements. No basics, and Zero Trust becomes Blind Trust.

I am interested in what others do with automation / #continousintegration and Zero Trust. Obviously the login secrets have to be stored in CI. And no one will ever check these CI logon logs, because these are too many.

Architecturally this is a challenge.

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/

#cicd #continousintegration #continousdelivery

Mesa, VirtualBox, Ceph, NetworkManager Packages Update in Tumbleweed https://news.opensuse.org/2019/06/06/mesa-virtualbox-ceph-networkmanager-packages-update-in-tumbleweed/ #continousintegration #openSUSETumbleweed #networkmanager #Announcements #Tumbleweed #WeeklyNews #ghashtable #mesonbuild #virtualbox #bublewrap #GNOME3.32 #snapshot #reviwer #malloc #fixes #GlibC #GNOME #Linux #ceph #curl #gegl #jsom #php7 #api #CVE #LTO

Un coup on me dit de prendre sur les setups sur Jenkins, un coup sur le nexus, un coup sur un serveur en mode partage réseau et maintenant un partage réseau directement sur le pc du collègue qui a développé la fonctionnalité.
J'adore la régularité des méthodes de livraison dans la boîte... #vieDeDev #continousIntegration #pasContinousDuToutVuCommeCa