Not being able to run your CI locally seems like a bit of a pain in the ass. I always end up with these N commit chains to fix simple problems in github actions because I can't just launch it locally and fix things the easy way.
Conversation
Notices
-
Embed this notice
Josh Simmons (dotstdy@mastodon.social)'s status on Monday, 29-Apr-2024 02:06:26 JST Josh Simmons -
Embed this notice
feld (feld@bikeshed.party)'s status on Monday, 29-Apr-2024 02:06:23 JST feld @TTimo just install gitlab-runner locally and run it yourself, it's easy. I think most people don't know this is possible ? -
Embed this notice
on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ (lain@lain.com)'s status on Monday, 29-Apr-2024 02:06:23 JST on-lain ✔ᵛᵉʳᶦᶠᶦᵉᵈ @feld @TTimo there’s also https://github.com/firecow/gitlab-ci-local which handles some more edge cases -
Embed this notice
Josh Simmons (dotstdy@mastodon.social)'s status on Monday, 29-Apr-2024 02:06:24 JST Josh Simmons @wolfpld @TTimo https://github.com/jsimmons/narcissus/actions :') I don't really mind the history, it just would have been much quicker to fix locally.
In conversation permalink Attachments
-
Embed this notice
TTimo (ttimo@mastodon.social)'s status on Monday, 29-Apr-2024 02:06:24 JST TTimo @dotstdy @wolfpld I run into a similar problem with gitlab runners. I sort of make it a requirement that I can ssh (or rdp to windows hosts), go to wherever it's building and fiddle with stuff locally until I have something that works.
In conversation permalink -
Embed this notice
TTimo (ttimo@mastodon.social)'s status on Monday, 29-Apr-2024 02:06:26 JST TTimo @dotstdy push force and squash, repeat ..
In conversation permalink -
Embed this notice
Bartosz Taudul (wolfpld@mastodon.gamedev.place)'s status on Monday, 29-Apr-2024 02:06:26 JST Bartosz Taudul In conversation permalink
-
Embed this notice