| Ci/CD is transforming right now but I don't think dagger is solving those things or I don't understand it well enough yet. GitHub action is a game changer. CICD finally has a proper UI were it belongs: on the repository. GitHub actions are also much easier than gitlab runner. The basic actions are great and probably solve 90% of all normal use cases. Then we/I see a big trend of going away from self build pipelines. Provide Standard Features through convention over configuration: the docker image build action checks if it need to run on the pipeline and runs isolated by default. The build packs are providing something like this but they are to clumsy/complex. Then you have the real issue no one is solving: - fast sync between stages and builds. 1 gb of source code, maven cache etc. Still need effort to do it fast. Preferable a filesystem which is fast and allows to share snapshots you can mount ober the network (it's not a big issue but puts a latency limit on how fast you can provide build results and I like it fast) - standard building blocks with retry mechanism. When a 3h build fails, restarting is annoying like hell. Pipelines have very little resilience. - unified CICD output: lots of plugins support Jenkins
Replacing Jenkins needs a new UI (GitHub has it now) which still is not unified. There is a thing going on to univy on GitHub through GitHub checks. I think in the next few years GitHub will have solved those issues for us. They do exactly what you are looking for. Would love to work with them. They even now inject the repository secret for you. They are slow (hello personal access token alternative we are waiting...) But steady. Btw. Before someone says gitlab: the Auto DevOps thing was shitty and bad supported. A default case with java and postgres was/is not fixed for 3 years. And those vulnerabilities. The last few years? Nope nope nope. |