2 ms·
> while others are stuck re-implementing various stages, tasks and blah blah blah. Also an added bonus to this is having the full history of changes to the CI/C
by est31 6y ago
> while others are stuck re-implementing various stages, tasks and blah blah blah. Also an added bonus to this is having the full history of changes to the CI/CD process tracked in git.
Can't those stages, tasks, etc. be specified in the CI specific config files of the repository? Specifying them via an UI seems horrible to me. At least Github actions is all file-specified (except for secrets).
- manigandham 6y agoIt still requires conversion of config files and formats vs a script that is the same everywhere.
- est31 6y agoYes, that's a valid point, and definitely a disadvantage. I was referring to the point that it's not tracked in git.