It's 3 AM, i just played a random argo workflow video, thinking that i will watch something that i already know, just to understand it better, since i am new to argo ecosystem, and then this - so brilliant solution, insanely good idea - executing argo workflows from existing pipelines, same can apply to bitbucket, azure ci/cd, etc..., thank you for this idea, it never comes to my mind, but i will definitely implement it! It will be nice if gitlab/github have API endpoints where you can POST results from your pipelines in another platform and make it look like they were runned like native ci/cd. :D
Hi! I'm new at Argo...I was wondering why not use just Gitlab CI rather than Argo? What's the difference? Benefits...I don't think I got that straight =/
We use Argo Workflows as we support GitHub also, and not just GitLab, but the main benefit is that it's a Kubernetes native CI engine. You can, however, use any other tools that make sense for you.
@@tadeubernacchi3360 Yes. Argo Workflows is a Kubernetes native workflows engine. People use it for a lot of reasons as it’s very good at orchestrating tasks at scale. Folks in the cloud native space regularly use it for machine learning, data science, task orchestration, and obviously, CI. On the kubefirst platform we only use it for CI, and we have some libraries that do all the stuff you’ll need to be able to do to deliver your code to a development, stage and production environment. We know our users will already be familiar with GitHub and GitLab, so we’ve integrated workflows with those products to produce a rich user experience in the developers’ existing Git provider environment. See github.com/kubefirst/gitops-template/tree/main/civo-github/templates/mgmt/components/argo-workflows/cwfts for our CWFTs. You can keep these automations and run CI like we do, or you can deviate run directly on GitHub Actions or GitLab runners, but you’ll have to duplicate what we did in Argo Workflows to use those products directly, if you are using kubefirst.
