News for hackers. Stuff that matters.

A comment on Travis CI's new pricing plan threw a wrench in my open source works. Parent comment

Re:Travis CI's new pricing plan threw a wrench in my open so... by est31 on Thursday November 05, 2020 @08:36PM (#25004003)
> 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).

[ Parent | on HN ]
Re:Travis CI's new pricing plan threw a wrench in my open so... by manigandham on Thursday November 05, 2020 @08:46PM (#25004065)
It still requires conversion of config files and formats vs a script that is the same everywhere.
[ Parent | on HN ]
Re:Travis CI's new pricing plan threw a wrench in my open so... by est31 on Thursday November 05, 2020 @08:59PM (#25004146)
Yes, that's a valid point, and definitely a disadvantage. I was referring to the point that it's not tracked in git.
[ Parent | on HN ]