Pinned post
Solomon Hykes
Verified account This account is verified. Learn more@solomonstre
15K Following 53K Followers 13K Posts
Latest posts 5
TONIGHT! We'll be talking about the future of CI from a systems engineer's perspective.
If you're in SF (perhaps for #AIEngineering code summit?) join us!
Thank you @recallai for hosting!
partiful.com/e/OfAlCP5IqgGT…
partiful.com RSVP to thou shalt not wait for CI | Partiful in the beginning, humans wrote the code. and the CI was slow, and it was wasteful, and we went to get coffee. then came the agents. and there was not enough coffee. but today, bear witness. Solomon... If you're in SF (perhaps for #AIEngineering code summit?) join us!
Thank you @recallai for hosting!
partiful.com/e/OfAlCP5IqgGT…
CI is a security risk because pipeline code is mixed with project code, so a pull request becomes a vector for untrusted code execution in your factory.
That made sense when code was a human input. Now that code is a generated artifact, it may have outlived its usefulness.
That made sense when code was a human input. Now that code is a generated artifact, it may have outlived its usefulness.
Another week, another forge integration! GitLab+Dagger has been a popular combo for years. But you had to jump through hoops to trigger checks after push.
No more!
Set up Dagger, connect accounts, and you're done. Run the same checks before and after push, with a shared cache.
No more!
Set up Dagger, connect accounts, and you're done. Run the same checks before and after push, with a shared cache.
Announcing Dagger for GitLab.View quoted post on X
Run the same checks before and after push. See results in your terminal and merge request.
Cut out the middleman: just GitLab and Dagger Cloud.
Stop wasting compute: checks are cached, and you pay for exact usage, not machines.
dagger.io/blog/dagger-fo…
Which git forge should Dagger integrate with next? 🤔