To be honest, my personal view is that the tool itself is less important that most others would tell. For me the decision is driven by several aspects that creates a storyline. This lead to questions like:
Where do I want to use CI/ CD?
Can my project be tested in a container?
Do I need special connectors to deploy it and is it supported?
Who triggers the CI/ CD?
Exist restrictions in accessing the solution (e.g. restricted workspace)?
And so on and so forth. Personally I like to do things my self, I like to know how and why things are working, I would like to extend my knowledge. But this comes at costs, you need to maintain your own landscape, you are pretty much likely restricted in accessing things from other places and there might be more restrictions as well. So speaking about my setup, in the past I developed Puppet modules using GitHub as a VCS and TravisCI for the build and deployment. The rationale was quite easy, TravisCI has a connector to deploy successful builds to the Puppet forge. As I still use GitHub and I like to have everything in one place, I try to migrate my CI/ CDs to GitHub Actions if possible. For me this is also the environment with the least restrictions, but as I already stated, this applies to my use case and might differ from case to case.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To be honest, my personal view is that the tool itself is less important that most others would tell. For me the decision is driven by several aspects that creates a storyline. This lead to questions like:
And so on and so forth. Personally I like to do things my self, I like to know how and why things are working, I would like to extend my knowledge. But this comes at costs, you need to maintain your own landscape, you are pretty much likely restricted in accessing things from other places and there might be more restrictions as well. So speaking about my setup, in the past I developed Puppet modules using GitHub as a VCS and TravisCI for the build and deployment. The rationale was quite easy, TravisCI has a connector to deploy successful builds to the Puppet forge. As I still use GitHub and I like to have everything in one place, I try to migrate my CI/ CDs to GitHub Actions if possible. For me this is also the environment with the least restrictions, but as I already stated, this applies to my use case and might differ from case to case.