agilob

I'm with OVH and Kimsufi and I don't know what you're even talking about. Do other providers make you install something locally?

I have this on my to-do list, but sorry, can't promise when I'll make a working demo. afair the trick was to use something like "podman in-podman", like dind works in GitLab runners and then some env-vars manipulation so TC thinks it runs in docker, something like

DOCKER_HOST=unix:///run/user/1000/podman/podman.sock and I use alpine as gitlab-ci helper image:

        image = "docker.io/alpine:3.17.2"
        helper_image_flavor = "alpine"

not sure if that matters, but i had lots of strange problems running with Ubuntu helper images, most were DNS propagation issues

Seems like you have some organizational and technical debt in the company that would be worth addressing before agreeing to be on-call

thats a really good deal, thanks for answering

Even for an outage starting at 2am lasting 6 hours?

I'll try to find it tomorrow

My tests that observe output from the method are failing so it's a breaking change. Did you not test the printed output?

I got it all working on self hosted kubernetes and crossplatform builds with buildah. What's your problem exactly? For TC you need to use some env vars to configure ports in .gitlabci

Fixed

This better shows what migration is like https://docs.scala-lang.org/scala3/guides/migration/incompat-syntactic.html

More, new brackets near lambdas, new string formatting, indentiation change. Doesn't look much, but absolute madness when your team is weak in Scala. Only 1 dev had prior scala experience, but whole team had to be involved in migration of breaking changes in scala syntax behavior and... same for gatling. Also changes in syntax. Mid-level dev left the company because of it, we very soon completely got rid of scala and replaced it with TS and Go. Both languages new to the team, but 0 complaints since February.

We had developers leave my company because they had to work with scala during 2 -> 3 migration. Everybody hates it now